geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Created: (GERONIMO-1165) Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
Date Sun, 13 Nov 2005 04:24:22 GMT
Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection

         Key: GERONIMO-1165
     Project: Geronimo
        Type: Bug
  Components: connector  
    Versions: 1.0-M5    
    Reporter: Aaron Mulder
 Assigned to: David Jencks 
     Fix For: 1.0

When playing with the system database pool size in the console, I got into a state where the
server was emitting the exceptions below every few minutes.  I had turned the max size of
that pool down from 100 to 65, and it was getting errors that it couldn't get a connection
within the timeout (which I had set to 4000 ms).

To replicate (not sure if this will definitely work):
 - Start Geronimo
 - Log in to the Console
 - Click "Database Pools" in the left nav
 - Click "Edit" next to "SystemDatasource" on the right
 - Change "Pool Max Size" to "65" and "Blocking Timeout" to "4000" and "IdleTimeout" to 1
 - Do something else for a few minutes and see if you end up getting any errors

I did this just now and did get the errors again, though I'm not 100% sure what the cause
is.  David Jencks suggested via IRC that it might be a bug with the pool resize code.

23:20:04,374 ERROR [JDBCPersistenceAdapter] Error in cleanup due to: java.sql.SQLException
        at org.tranql.connector.jdbc.DataSource.getConnection(
        at $javax.sql.DataSource$$FastClassByCGLIB$$6525cafd.invoke(<generated>)
        at net.sf.cglib.proxy.MethodProxy.invoke(
        at org.apache.geronimo.connector.ConnectorMethodInterceptor.intercept(
        at $javax.sql.DataSource$$EnhancerByCGLIB$$9ea1bb9a.getConnection(<generated>)
        at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$ Source)
Caused by: No ManagedConnections available within configured blocking timeout ( 4000 [ms]
        at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(
        at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(
        at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(
        at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(
        at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(
        at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(
        at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(
        at org.tranql.connector.jdbc.DataSource.getConnection(
        ... 9 more                                                              

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message