I use jboss3.0 alpha.
JBoss never calls ManagedConnection.destory()..
what is the reason for??
Am I doing anything wrong??
It is doing cleanup connections but not destroying connection.
I checked my-adapter-service.xml,there I could specify cleanup interval but not destroying time references...
Can anybody help me??
Thanks in advance,
The pooling code is .... not my favorite. I hadn't seen the lack of blocking/exception problem before. I am working on replacement pooling code and will try to check for this problem in it.
You should be able to cause your ManagedConnections to be destroyed after a period of inactivity using IdleTimeout. Do you see a need to destroy connections that are of sufficient age even if they are being regularly used? Is the idle timeout working for you?
thanks if you could check once again pooling code.
And coming to ManagedConnection.destroy()..
As you mentioned idle timeout,it does n't work.I put
IdleTimeoutMinutes=2, but it never called destory() in ManagedConnection, even in a whole day idle time.
The interesting thing here is after some time( I don't know, only just jboss pooling implementation knows,suppose 20min)it deletes the mgdconnection object without intimating my managed connection.detroy().Then if I call once again javax.resource.cci.ConnectionFactory.getConnection() then jboss connection pool creates new managed connection and works fine.If you delete the mgdconnection object without intimating ManagedConnection.destory(),its not good.How can u close physical connection,just deleting the object from pool??
I am using MinervaNoTransCMFactory.