Exhaustion of the pool of available connections - the application during idle times

[zerdo]

Hello,

We use jboss-as-7.1.1.Final on several environments. In a production environment (as usual on the production of the most interesting problems!) There is a problem with the lack of a free connection pool.

We found that it is not feasible to run at the time of these connections because max pool size was set to 20 and the problem appeared when trying to input by 1 user.

At 100% no one at the moment does not perform other operations, and the application was idle.

In the administrative console, you can see that jboss connection pool is actually exhausted, even though no one is using the application.

Is there a way to break the connection pool?

How can I force a periodic severing connections?

How to protect yourself from such a situation?

[welle]

I would start with creating a thread dump and analyzing which threads (if any) that are running (hanging) that may responsible for not giving the connection back.

[zerdo]

I do not understand what you mean. In the logs on jboss nothing happens. - Otherwise the exception of the exhaustion of free calls when you try to log into the application.

[welle]

> In the administrative console, you can see that jboss connection pool is actually exhausted

This is when the problem occurred I believe? This is when you should do a thread dump to be able

to analyze what threads i that may be using the connections from the pool.

Have you looked at the pool values from time to time when the application is "unused"? Are all connections

available and than all of a sudden they are all used, even if the application is "sleeping"?