db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4303) Handful of replication tests failed because they failed to get a connection to the slave within two minutes.
Date Wed, 15 Jul 2009 12:47:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731421#action_12731421
] 

Knut Anders Hatlen commented on DERBY-4303:
-------------------------------------------

>From the slave log, it looks like the slave failed to start because the slave port (1532
in this test) was already in use, see the exception below. Start master therefore failed repeatedly
with connection refused until the test gave up after two minutes.

java.net.BindException: Address already in use: NET_Bind

	at java.net.PlainSocketImpl.socketBind(Native Method)

	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:415)

	at java.net.ServerSocket.bind(ServerSocket.java:331)

	at java.net.ServerSocket.<init>(ServerSocket.java:197)

	at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:2)

	at org.apache.derby.impl.store.replication.net.ReplicationMessageReceive$2.run(Unknown Source)

	at java.security.AccessController.doPrivileged(AccessController.java:246)

	at org.apache.derby.impl.store.replication.net.ReplicationMessageReceive.createServerSocket(Unknown
Source)

	at org.apache.derby.impl.store.replication.net.ReplicationMessageReceive.initConnection(Unknown
Source)

	at org.apache.derby.impl.store.replication.slave.SlaveController.setupConnection(Unknown
Source)

	at org.apache.derby.impl.store.replication.slave.SlaveController.startSlave(Unknown Source)

	at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)

	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)

	at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)

	at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown Source)

	at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown Source)

	at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown Source)

	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)

	at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)

	at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown Source)

	at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown Source)

	at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)

	at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)

	at org.apache.derby.impl.db.SlaveDatabase.bootBasicDatabase(Unknown Source)

	at org.apache.derby.impl.db.SlaveDatabase.access$000(Unknown Source)

	at org.apache.derby.impl.db.SlaveDatabase$SlaveDatabaseBootThread.run(Unknown Source)

	at java.lang.Thread.run(Thread.java:810)


> Handful of replication tests failed because they failed to get a connection to the slave
within two minutes. 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4303
>                 URL: https://issues.apache.org/jira/browse/DERBY-4303
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.0.0
>            Reporter: Mamta A. Satoor
>         Attachments: master_and_slave_logs.zip
>
>
> The nightly runs on trunk(revision 793163) using ibm15 had 19 failures in replication
tests (all failing for same reason
> junit.framework.AssertionFailedError: startMaster did not succeed.)  Copying Knut's comments
to the failure
> **************
> It looks like all the failing tests failed to get a connection to the
> slave within two minutes. There may be more information in derby.log on
> the slave or on the master (should be available in the fail
> directory). It's probably best to log a JIRA issue and attach the
> information there. This is not one of the known replication test
> failures, I think, but since they all fail the same way it sounds likely
> that there is some test cleanup code that doesn't properly release all
> resources or an environment problem of some kind.
> **************

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message