| 2013-10-23 07:01:40 |
David Katuscak |
bug |
|
|
added bug |
| 2013-10-23 07:04:19 |
David Katuscak |
description |
Application (1 test component) is using BoneCP connection pool. All the things are usually working fine (getting connection, releasing, ....) but sometimes in the random time happen that some connection is spontaneously closed.
This is the output from log4j:
-----------------------------------------------------------------------------------------------
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1013)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927)
at com.mysql.jdbc.ConnectionImpl.throwConnectionClosedException(ConnectionImpl.java:1205)
at com.mysql.jdbc.ConnectionImpl.checkClosed(ConnectionImpl.java:1197)
at com.mysql.jdbc.ConnectionImpl.createStatement(ConnectionImpl.java:2483)
at com.mysql.jdbc.ConnectionImpl.createStatement(ConnectionImpl.java:2465)
at com.betradar.database.SportradarConnection.createStatement(SportradarConnection.java:218)
at com.jolbox.bonecp.ConnectionHandle.createStatement(ConnectionHandle.java:718)
at com.oddsarbitrage.livescore.hotnessfactor.HotnessFactorComponent.calculateOverallFactors(HotnessFactorComponent.java:181)
at com.oddsarbitrage.livescore.hotnessfactor.HotnessFactorComponent.access$1000(HotnessFactorComponent.java:28)
at com.oddsarbitrage.livescore.hotnessfactor.HotnessFactorComponent$ProcessMatches.run(HotnessFactorComponent.java:139)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
-----------------------------------------------------------------------------------------------
So I don't know if it is bug, or just some configuration issue about liveness of the connection.
Idle timeout is set to 60 seconds, min connections = 2, max connections = 5.
When the connection was closed, it was normally used by 1 thread of application, so it wasn't in the pool, so I think that it should not be closed spontaneously.
Thanks for reply. |
Application (1 test component) is using BoneCP connection pool. All the things are usually working fine (getting connection, releasing, ....) but sometimes in the random time happen that some connection is spontaneously closed.
This is the output from log4j:
-----------------------------------------------------------------------------------------------
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1013)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927)
at com.mysql.jdbc.ConnectionImpl.throwConnectionClosedException(ConnectionImpl.java:1205)
at com.mysql.jdbc.ConnectionImpl.checkClosed(ConnectionImpl.java:1197)
at com.mysql.jdbc.ConnectionImpl.createStatement(ConnectionImpl.java:2483)
at com.mysql.jdbc.ConnectionImpl.createStatement(ConnectionImpl.java:2465)
at com.radar.database.Connection.createStatement(Connection.java:218)
at com.jolbox.bonecp.ConnectionHandle.createStatement(ConnectionHandle.java:718)
at com.arbitrage.live.factor.FactorComponent.calculateOverallFactors(FactorComponent.java:181)
at com.arbitrage.live.factor.FactorComponent.access$1000(FactorComponent.java:28)
at com.arbitrage.live.factor.FactorComponent$ProcessMatches.run(FactorComponent.java:139)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
-----------------------------------------------------------------------------------------------
So I don't know if it is bug, or just some configuration issue about liveness of the connection.
Idle timeout is set to 60 seconds, min connections = 2, max connections = 5.
When the connection was closed, it was normally used by 1 thread of application, so it wasn't in the pool, so I think that it should not be closed spontaneously.
Thanks for reply. |
|
| 2013-10-31 09:50:14 |
Wallace Wadge |
bonecp: status |
New |
Triaged |
|
| 2013-10-31 09:50:20 |
Wallace Wadge |
bonecp: importance |
Undecided |
Medium |
|
| 2013-10-31 09:50:22 |
Wallace Wadge |
bonecp: assignee |
|
Wallace Wadge (wwadge) |
|
| 2013-10-31 11:42:59 |
Pierre |
bug |
|
|
added subscriber Pierre |
| 2013-11-03 14:32:32 |
Steven |
bug |
|
|
added subscriber Steven |
| 2013-11-14 17:06:14 |
Andrew Conner |
bug |
|
|
added subscriber Andrew Conner |
| 2013-12-03 12:38:57 |
Ólafur Gauti Guðmundsson |
bug |
|
|
added subscriber Ólafur Gauti Guðmundsson |
| 2013-12-12 08:52:15 |
Damien Hostin |
bug |
|
|
added subscriber Damien Hostin |
| 2014-01-13 17:01:23 |
Martin Burger |
bug |
|
|
added subscriber Martin Burger |
| 2014-01-22 17:22:58 |
Matt Sgarlata |
attachment added |
|
stack trace.txt https://bugs.launchpad.net/bonecp/+bug/1243551/+attachment/3954570/+files/stack%20trace.txt |
|
| 2014-01-22 17:24:50 |
Matt Sgarlata |
attachment added |
|
CreateIndexesUpgradeTask.java https://bugs.launchpad.net/bonecp/+bug/1243551/+attachment/3954571/+files/CreateIndexesUpgradeTask.java |
|
| 2014-01-26 10:24:48 |
Alexander Azarov |
bug |
|
|
added subscriber Alexander Azarov |
| 2014-03-15 21:23:41 |
David Alvarado |
attachment added |
|
SQLServerException stack trace https://bugs.launchpad.net/bonecp/+bug/1243551/+attachment/4026061/+files/exceptions.txt |
|
| 2014-03-17 13:42:58 |
Micael Paquier |
bug |
|
|
added subscriber Micael Paquier |
| 2014-04-14 12:16:31 |
Christophe Bram |
bug |
|
|
added subscriber Christophe Bram |
| 2014-04-24 00:48:43 |
Tushar Jain |
bug |
|
|
added subscriber Tushar Jain |
| 2014-04-24 05:31:43 |
Brian KimJohnson |
bug |
|
|
added subscriber Brian KimJohnson |
| 2014-07-26 10:41:59 |
draiwn |
bug |
|
|
added subscriber draiwn |
| 2014-11-06 16:57:51 |
RC |
bug |
|
|
added subscriber RC |
