No ManagedConnections available ...

[rolfz]

Hi

After around 18 hours of stress testing we receive a few of thoses errors and then the whole JBoss server just stops and tries to terminate.

My first thought was that I leave some db connection open until none are available but I double check the code and I also don't get any " closing connection for you .." messages in the log file.

Then I checked if I perform some action after a transaction is marked as Rollback due to this bug in the earlier version but it seems fine as well.

I also check the memory usage, which seems fine as well

Now I'm at the end of my wisdom and seek for help here. Is there a way how to check the number of currently used connection from a pool or do you have any suggestions for further investigations.

Thanks
Rolf

[rolfz]

Sorry forgot my system configurations:

W200 Server (1 GB Ram) + JBoss 3.2.5.

[kalyan120]

The JMX Console shows you the number of connections used, created, etc. for the Connection pool. Also, did you check if your database server has run out of connections?

Thanks,
Kalyan

[chris_pollentier]

We had the same issue. This is related to a bug in Jboss ConnectionPool.

The bug has been fixed in jboss 3.2.6

For details:
http://sourceforge.net/tracker/index.php?func=detail&aid=985318&group_id=22866&atid=376685

[rolfz]

Well I upgraded to 3.2.6 but still have the same issue after around 15-19 hours of stress testing

Any other suggestions ?

[adrian.brock]

1) Read the FAQ on how to enable "closing a connection for you" in the web layer
2) Use READ THIS FIRST to get TRACE information for org.jboss.resource
one part of which shows the evolution of the pool.

[adrian.brock]

Additionally, read the FAQ on the other courses of this message, beyond not closing
connections. e.g. long GCs

[nchadwick]

link to the FAQ please.

[anil.saldhana]

http://www.jboss.org/index.html?module=bb&op=viewforum&f=136

At the beginning of the forum, you should see sticky tags that are usually for FAQ.