You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/11/13 05:24:22 UTC
[jira] Created: (GERONIMO-1165) Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
------------------------------------------------------------------------------
Key: GERONIMO-1165
URL: http://issues.apache.org/jira/browse/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
java.sql.SQLException
at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:61)
at $javax.sql.DataSource$$FastClassByCGLIB$$6525cafd.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.apache.geronimo.connector.ConnectorMethodInterceptor.intercept(ConnectorMethodInterceptor.java:53)
at $javax.sql.DataSource$$EnhancerByCGLIB$$9ea1bb9a.getConnection(<generated>)
at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:417)
at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
at java.lang.Thread.run(Thread.java:552)
Caused by: No ManagedConnections available within configured blocking timeout ( 4000 [ms] )
at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:73)
at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:47)
at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:86)
at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43)
at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66)
at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:58)
at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56)
... 9 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1165) Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1165?page=all ]
David Jencks closed GERONIMO-1165:
----------------------------------
Fix Version: 1.1
Resolution: Fixed
head:
Sending modules/connector/src/java/org/apache/geronimo/connector/outbound/AbstractSinglePoolConnectionInterceptor.java
Transmitting file data .
Committed revision 356110.
1.0
fixed, lost rev. #.
> Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
> ------------------------------------------------------------------------------
>
> Key: GERONIMO-1165
> URL: http://issues.apache.org/jira/browse/GERONIMO-1165
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M5
> Reporter: Aaron Mulder
> Assignee: David Jencks
> Fix For: 1.0, 1.1
>
> 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 and click "Save"
> - Do something else for a few minutes and see if you end up getting any errors printed to the server stdout
> 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
> java.sql.SQLException
> at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:61)
> at $javax.sql.DataSource$$FastClassByCGLIB$$6525cafd.invoke(<generated>)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
> at org.apache.geronimo.connector.ConnectorMethodInterceptor.intercept(ConnectorMethodInterceptor.java:53)
> at $javax.sql.DataSource$$EnhancerByCGLIB$$9ea1bb9a.getConnection(<generated>)
> at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:417)
> at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
> at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
> at java.lang.Thread.run(Thread.java:552)
> Caused by: No ManagedConnections available within configured blocking timeout ( 4000 [ms] )
> at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:73)
> at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:47)
> at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:86)
> at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43)
> at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
> at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66)
> at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:58)
> at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56)
> ... 9 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1165) Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1165?page=all ]
Aaron Mulder updated GERONIMO-1165:
-----------------------------------
Description:
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 and click "Save"
- Do something else for a few minutes and see if you end up getting any errors printed to the server stdout
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
java.sql.SQLException
at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:61)
at $javax.sql.DataSource$$FastClassByCGLIB$$6525cafd.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.apache.geronimo.connector.ConnectorMethodInterceptor.intercept(ConnectorMethodInterceptor.java:53)
at $javax.sql.DataSource$$EnhancerByCGLIB$$9ea1bb9a.getConnection(<generated>)
at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:417)
at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
at java.lang.Thread.run(Thread.java:552)
Caused by: No ManagedConnections available within configured blocking timeout ( 4000 [ms] )
at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:73)
at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:47)
at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:86)
at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43)
at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66)
at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:58)
at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56)
... 9 more
was:
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
java.sql.SQLException
at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:61)
at $javax.sql.DataSource$$FastClassByCGLIB$$6525cafd.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.apache.geronimo.connector.ConnectorMethodInterceptor.intercept(ConnectorMethodInterceptor.java:53)
at $javax.sql.DataSource$$EnhancerByCGLIB$$9ea1bb9a.getConnection(<generated>)
at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:417)
at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
at java.lang.Thread.run(Thread.java:552)
Caused by: No ManagedConnections available within configured blocking timeout ( 4000 [ms] )
at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:73)
at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:47)
at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:86)
at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43)
at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66)
at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:58)
at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56)
... 9 more
> Changing System DB pool size to 65 causes ActiveMQ to fail to get a connection
> ------------------------------------------------------------------------------
>
> Key: GERONIMO-1165
> URL: http://issues.apache.org/jira/browse/GERONIMO-1165
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0-M5
> Reporter: Aaron Mulder
> Assignee: 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 and click "Save"
> - Do something else for a few minutes and see if you end up getting any errors printed to the server stdout
> 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
> java.sql.SQLException
> at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:61)
> at $javax.sql.DataSource$$FastClassByCGLIB$$6525cafd.invoke(<generated>)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
> at org.apache.geronimo.connector.ConnectorMethodInterceptor.intercept(ConnectorMethodInterceptor.java:53)
> at $javax.sql.DataSource$$EnhancerByCGLIB$$9ea1bb9a.getConnection(<generated>)
> at org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:417)
> at org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
> at org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
> at java.lang.Thread.run(Thread.java:552)
> Caused by: No ManagedConnections available within configured blocking timeout ( 4000 [ms] )
> at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:73)
> at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:47)
> at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:86)
> at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43)
> at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39)
> at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66)
> at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:58)
> at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56)
> ... 9 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira