This one time, at band camp, Arun Sudhakaran said:

AS>    I'd tested Castor 0.9.4 for the managed connections bug which was reported to 
have been fixed in this release. I used Castor with Jboss 3.0.0. I'd set the 
connection pool size to 5. i tried concurrently accessing the same resource and 
received the follwing exception : 
AS>
AS>javax.resource.ResourceException: No ManagedConnections Available!
AS>        at 
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:122)
AS>        at 
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:312)
AS>        at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:467)
AS>        at 
org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:221)
AS>        at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:532)
AS>        at 
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:812)
AS>        at 
org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:102)
AS>        at org.exolab.castor.jdo.engine.DatabaseRegistry.createConnection(Unknown 
Source)
AS>        at 
org.exolab.castor.jdo.engine.TransactionContextImpl.getConnection(Unknown Source)
AS>        at org.exolab.castor.persist.TransactionContext.query(Unknown Source)       
 at org.exolab.castor.jdo.engine.OQLQueryImpl.execute(Unknown Source)
AS>
AS>Since the connection management is being done by close() method in 
org.exolab.castor.jdo.engine.DatabaseImpl.java i'd checked it out and found that the 
else statement is still missing. ie,what would happen when the context is not null and 
is open. So i guess the problem still remains :-(

Arun, 

I just refixed bug #1031. That dealt with connections not being returned
to the pool when container managed transactions roll back. I remember this
issue that you speak of, but I am unable to find anything in Bugzilla
(http://bugzilla.exolab.org/). Was there a bug filed on this? 

Bruce
-- 
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to