I'm going through the process of migrating an app from JBoss 2.4.4 to JBoss 3.0.4, and have hit a behavior difference regarding the use of connection pools.
Normally, we would get a connection from the pool within a bean and continue to use that connection until the bean is deactivated, at which time the connection is returned to the pool. This was working under JBoss 2.4.4.
The same code under JBoss 3.0.4 throws an exception if I do not call close() on the pool connection after I use it for a query, insert or update and get a fresh connection for the next use within the bean:
16:27:45,847 ERROR [LogInterceptor] RuntimeException:
java.lang.IllegalArgumentException: disconnect(ManagedConnection mc: null, Object c: org.jboss.resource.adapter.jdbc.local.LocalConnection@4b2185) called with unknown managed connection
Is there some additional configuration that I need for the datasource/connection pool in order to be able to reuse a pool connection without returning it to the pool?
My basic pool attributes are:
MinSize = 0
MaxSize = 10
BlockingTimeoutMillis = 5000
IdleTimeoutMinutes = 15
Criteria = ByContainer
Below is the config for one of the pools under JBoss 2.4.4 . Perhaps there's a configurable used in this old config that I need a JBoss 3.x equivalent for in my new config? I haven't found anything obvious in the docs or forum yet.
Finally, has anyone else noticed the JBoss forum search not working as of 11/12/2002? It's been this way for about a week.