I've recently migrated our application from JBoss 3.2.4 to 3.2.7 and now 4.0.1.
We are actively trying to solve a deadlock issue that is rearing its head too
frequently.
We are using the Standard 2.X Entity Bean configuration with commit option A
and QueuedPessimistic locking. The problem appe
My fix for this, which appears to work for the few tests I've run.
is to upgrade to the 8.0 jdbc driver.
and
append ?protocolVersion=2 to the jdbc url in your datasource configuration.
You may not have to do the latter but it threw some exceptions for me b/c the
db column was boolean and the
Where you able to get around it?
Everytime I deploy I seem to get the same error. I'm going to try it against
oracle tommorow and see if I get the same error.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866860#3866860
Reply to the post :
http://www.jbos
I've just done a first pass at migrating an existing application from 3.2.7 to
4.0.1.
Has anyone ran in to the "The backend currently does not support this feature."
when running 4.0.1 against PostgreSQL 7.4.X.
I haven't made any changes to the jar file beyond re-compiling, is there some
plac
I'm having similar problems with the HTTPConnectionFactory.
JBoss is running on an internal NAT'd machine. I need to be able to run JMS over 8080
to facilitate someone from outside the firewall to be able to receive messages.
I've made the following client side changes:
Properties props = new
