You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Prasenjit Sarkar (JIRA)" <de...@db.apache.org> on 2006/09/01 20:36:22 UTC
[jira] Created: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Connection errors in 10.2.1.1 - not seen in 10.1.2.1
----------------------------------------------------
Key: DERBY-1806
URL: http://issues.apache.org/jira/browse/DERBY-1806
Project: Derby
Issue Type: Bug
Affects Versions: 10.2.1.0
Environment: WinXP 2G RAM 2.8 GHz dual PIV
Reporter: Prasenjit Sarkar
Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
Details from our test team:
The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
Please ensure that the repository database is up
and running.
Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
URL : jdbc:derby://tivoli14:1527/Aperi
SQLSTATE: 08001, Vendor error code: -4499
java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
I think the problem is critical enough and should be fixed ASAP.
Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
Thu Aug 31 15:33:03 PDT 2006
java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
at org.apache.derby.client.am.Connection.<init>(Unknown Source)
at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
... 10 more
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
--
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] Commented: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510534 ]
Kathey Marsden commented on DERBY-1806:
---------------------------------------
I wonder if this issue can be closed since the user was not able to reproduce?
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: https://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.2.1.6
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=comments#action_12432695 ]
Kathey Marsden commented on DERBY-1806:
---------------------------------------
Hi Prasenjit,
Can you please post a reproducible case for this issue. Certainly there are tests with multiple connections so there is probably some specific scenario that causes this to occur.
Thanks for your great work hashing out issues with 10.2. Please make sure you add the bugs you have found to http://wiki.apache.org/db-derby/RegressionSearchAndDestroy?highlight=%28RegressionSearchAndDestroy%29
so they get considered in the RegressionSearchAndDestroyContest and so we have a good picture of our user feedback for the release.
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.0
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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] Resolved: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-1806.
-----------------------------------
Resolution: Cannot Reproduce
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: https://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.2.1.6
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Rajesh Kartha (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=comments#action_12432908 ]
Rajesh Kartha commented on DERBY-1806:
--------------------------------------
Can you please post the derby.log file from the server. I suspect something happened during one of the earlier connections and
the Network server went into a hang/crash (?).
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.0
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
> Fix For: 10.2.1.0
>
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-1806:
----------------------------------
Component/s: Network Server
Network Client
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: https://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.2.1.6
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Prasenjit Sarkar (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=comments#action_12433514 ]
Prasenjit Sarkar commented on DERBY-1806:
-----------------------------------------
We have not been able to replicate this issue since the first discovery, once we do, we will send all relevant files...
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.0
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
> Fix For: 10.2.1.0
>
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ]
Rick Hillegas updated DERBY-1806:
---------------------------------
Fix Version/s: 10.2.1.0
Assign to 10.2.
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.0
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
> Fix For: 10.2.1.0
>
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ]
Rick Hillegas updated DERBY-1806:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.0
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
> Fix For: 10.2.2.0
>
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ]
Rick Hillegas updated DERBY-1806:
---------------------------------
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.6
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
> Fix For: 10.2.3.0
>
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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: (DERBY-1806) Connection errors in 10.2.1.1 - not
seen in 10.1.2.1
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ]
Rick Hillegas updated DERBY-1806:
---------------------------------
Urgency: Normal (was: Urgent)
Downgrading the urgency of this issue because no reproducible test-case has surfaced.
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ----------------------------------------------------
>
> Key: DERBY-1806
> URL: http://issues.apache.org/jira/browse/DERBY-1806
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.0
> Environment: WinXP 2G RAM 2.8 GHz dual PIV
> Reporter: Prasenjit Sarkar
> Fix For: 10.2.1.0
>
>
> Essentially the Derby 10.2 beta is unable to handle multiple connections to it - when we have a large number of connections to the db, we get stale connection errors, not observed in 10.1
> Details from our test team:
> The problem I am running into is that if I submit two storage subsystem probes at the same time, the jobs may not finish and show the following errors
> 8/31/06 3:33:11 PM SRV0044E: Unable to connect to repository database.
> Please ensure that the repository database is up
> and running.
> Driver: org.apache.derby.jdbc.ClientDriver@7ecd78
> URL : jdbc:derby://tivoli14:1527/Aperi
> SQLSTATE: 08001, Vendor error code: -4499
> java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> 8/31/06 3:33:11 PM STS0079E: Unable to run job ExecProbeSS.
> I think the problem is critical enough and should be fixed ASAP.
>
> Thu Aug 31 15:32:52 PDT 2006 Stale connection encountered = org.apache.derby.client.net.NetConnection@3f2ce6
> Thu Aug 31 15:33:03 PDT 2006
> java.sql.SQLException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:300)
> at org.eclipse.aperi.infrastructure.database.Database.getConnection(Database.java:267)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource$Pool.remove(DBConnPoolDataSource.java:306)
> at org.eclipse.aperi.infrastructure.database.DBConnPoolDataSource.getPooledConnection(DBConnPoolDataSource.java:110)
> at org.eclipse.aperi.ServiceUtils.getConnection(ServiceUtils.java:314)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.getTargets(SNMPAgentManager.java:647)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.refreshAllIpTargetCapabilities(SNMPAgentManager.java:988)
> at org.eclipse.aperi.snmpagent.manager.SNMPAgentManager.run(SNMPAgentManager.java:1694)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.derby.client.am.DisconnectException: java.net.BindException : Error connecting to server tivoli14 on port 1527 with message Address already in use: connect.
> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)
> at org.apache.derby.client.am.Connection.<init>(Unknown Source)
> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
> ... 10 more
> Caused by: java.net.BindException: Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
--
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