-
1. Re: No ManagedConnections available within configured blocking timeout in Jboss 4.0.1 sp1
wdfink Nov 5, 2013 2:44 AM (in response to koolkhalid)I'm not sure what can be the cause.
The blocking timeout of 60,000ms seems very long, I dit not want to wait 60sec for the next free connection. You might reduce it to a couple of ms that you can see if there are threads waiting for it.
Do you see that the connections are fully used?
-
2. Re: No ManagedConnections available within configured blocking timeout in Jboss 4.0.1 sp1
koolkhalid Nov 13, 2013 4:11 AM (in response to wdfink)Hi Fink,
Thanks for your feedback. On blocking timeout, while googling i checked various developers who set this on 30sec they are also making complaints of the same error 'No managed Connection'. Would it be better to make it 30sec. I am unable to understand by term connections are fully used? kindly clarify. Secondly, jmx-console is not working properly with jboss, now i am looking to attach Java Melody to check connection pool manager MBean properties for ConnectionCount, AvailableConnectionCount, MaxConnectionInUseCount, InUseConnectionCount.
Please help me to fix this OR guide any other workaround that can be used to get rid of this issue.
Thanks.
-
3. Re: No ManagedConnections available within configured blocking timeout in Jboss 4.0.1 sp1
wdfink Nov 14, 2013 11:48 AM (in response to koolkhalid)If you look to the jmx- or management-console you wil find the pools under the JCA point.
You can see different configuration options here and also the number of connections that are current in use and the max of used connections.
"Fully used" mean the pool does not have more connections (all are busy).
Busy might mean the application does not close it (this mean here the connection is not longer in use and will be back to the pool)
Now the blocking timout come into play, this time mean how long the getConnection should wait for a free connection if there is no available in the pool.
So a long blocking timeout might only hide a performance problem if there are too many parallel requests. But if you havn't such huge access this mean you have a leak and the connections are not going back to pool.
In that case you need to check the application whether the connection/statements are closed in ANY case after use
-
4. Re: No ManagedConnections available within configured blocking timeout in Jboss 4.0.1 sp1
koolkhalid Feb 13, 2014 8:19 AM (in response to wdfink)Hi Fink,
Sorry for late reply, i am attaching connection pool details showing connection details along with connections destroyed count. It seems that connections are closing but i am still getting same error of 'No Managed Connection'. As per your suggestion additionally i will also check that statements are closed or not?
But, you please share your opinion on this.
Thanks.