DefaultDS

riandort Feb 17, 2005 10:09 AM

We have a system deployed on Jboss 3.2.6 that uses JMS queues to log audit information into a database. (It uses other queues for other things as well) After some time of running, the log writer queue reports the following:

2005-02-04 15:41:07,831 ERROR [org.jboss.security.auth.spi.DatabaseServerLoginModule] SQL failure
org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.Reso
urceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))

It seems that the it has run out of hsql connections to authenticate the user (always null/null).

Nobody uses this data source other than jboss. There is no unusual load on the system that could cause this. How can this pool run out of connections, and why does this condition last for 10 days? (after which the jboss instance has been restarted)

1. Re: Jboss/JMS out of managed connections on java:/DefaultDS

razor_harm Feb 18, 2005 9:43 AM (in response to riandort)

Can you reproduce this behaviour when you use a 'real' database such as MySQL, PostgreSQL or Oracle? Hypersonic is not a production ready database. It is only shipped with JBoss to have something working out-of-the-box.
Actions
2. Re: Jboss/JMS out of managed connections on java:/DefaultDS

adrian.brock Feb 18, 2005 7:48 PM (in response to riandort)

Moderated: FAQ (both JCA and JBossMQ)
Actions
3. Re: Jboss/JMS out of managed connections on java:/DefaultDS

informsantosh Mar 3, 2005 8:09 AM (in response to riandort)

Hi the error you will face coz of following configuration

<blocking-timeout-millis >30000 </blocking-timeout-millis >
Increase the value of timeout to 80000
Actions
4. Re: Jboss/JMS out of managed connections on java:/DefaultDS

anil.saldhana Mar 3, 2005 11:02 AM (in response to riandort)

As Adrian pointed out, please have a look at the FAQ at the beginning of this forum.

Changing the blocking timeout is not the solution to database connection management. Keep your database connection ops short and always return the connection to the pool.

Also ensure that you have a "finally" block where you close the connections.
Actions

Go to original post