[
https://issues.apache.org/jira/browse/DERBY-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733298#action_12733298
]
Kathey Marsden commented on DERBY-4303:
---------------------------------------
Both times this happened we first got this failure: 1)
ttestSetPortPriority(org.apache.derbyTesting.functionTests.tests.derbynet.ServerPropertiesTest)junit.framework.AssertionFailedError:
Timed out waiting for network server to start
Which did have a bind exception on port 1533 which I think was what the
replication test was using. I thought that where
TestConfiguration.getCurrent().getNextAvailablePort() was used it just kept
incrementing and would not reuse the same port.
2009-07-19 03:18:21.139 GMT : Could not listen on port 1533 on host localhost:
java.net.BindException: Address already in use: NET_Bind
An exception was thrown during network server startup. DRDA_ListenPort.S:Could
not listen on port 1533 on hos
java.net.BindException: Address already in use: NET_Bind
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.derby.iapi.jdbc.DRDAServerStarter.run(Unknown Source)
at java.lang.Thread.run(Thread.java:810)
Caused by: java.lang.Exception: DRDA_ListenPort.S:Could not listen on port 1533
on host localhost:
java.net.BindException: Address already in use: NET_Bind
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(Unknown
Source)
... 5 more
An exception was thrown during network server startup. null
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.derby.iapi.jdbc.DRDAServerStarter.run(Unknown Source)
at java.lang.Thread.run(Thread.java:810)
Caused by: java.lang.NullPointerException
at
org.apache.derby.impl.drda.NetworkServerControlImpl.isMsgProperty(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.localizeMessage(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(Unknown
Source)
... 5 more
> 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.
