java - Is there a way to release a saturated connection pool? -


I am working with Open ASB on a glassfish server. We have a connection pool that works with an AS400 database.

Every two days we get this error: Error in allocating the connection. Reason: The maximum-pool-size equal to the in-use connection and the maximum-waiting-time ended Can not allocate more connections

The best way to relieve the CP is to restart the server. We have been successful in the other CP with the same features.

My question is: is there any way to actively "tell" CPE to release all its open connections?

Cheers, Eran

Before doing this, find out Why not leave the connection properly? It seems as if there is a place where it has forgotten (Do you have the closure in the end?).

I strongly recommend "this release" to Michael Nigords! Techniques To Create Software Production Edit # 1: If I understand your description correctly, your backend program goes to MSGW in QSYSOPR, which results in a response to the hanging, as long as your The matter is not close. to never. Is it the option to use a profile with a default answer to "C", which, as an exception, allows the error to be propagated by you?

Otherwise, you might be able to set a timeout period for either the connection or for the entire 24-hour server? Then at least connections will eventually be closed. Although this solution is not on the scale, but the development can be easy.

Please note, it is possible to have a separate surveillance pouch that regularly visits MSGW and for call back stack post-mortem analysis.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -