db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1806) Connection errors in 10.2.1.1 - not seen in 10.1.2.1
Date Tue, 05 Sep 2006 23:46:24 GMT
    [ 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

        

Mime
View raw message