[
https://issues.apache.org/jira/browse/DERBY-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700873#action_12700873
]
Suran Jayathilaka commented on DERBY-4053:
------------------------------------------
When testing client/server compatibility with 10.5.1.1.-rc2 and 10.4.2.0 I
encountered what seems to be a reproduction of this issue.
Environment: AMD Phenom II Quad Core CPU, 4GB Ram, Vista 64
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
Client - 10.4.2.0. Jars
-------------------
derbyTesting.jar
derbyClient.jar
Server - 10.5.1.1. Jars
-------------------
derby.jar
derbynet.jar
derbytools.jar
derbyLocale*.jar
derbyrun.jar
XA40Test.testCallableStatementPoolable fails with the following exception. And
then the suite hangs.
-----------------------------------------------------------------------------------------------------
testPreparedStatementPoolable used 1 ms .
testCallableStatementPoolable used 2 ms java.lang.Exception:
DRDA_InvalidReplyTooShort.S:Invalid reply from network server: Insufficient
data.
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.fillReplyBuffer(Unknown
Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Unknown Source)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(Unknown
Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(Unknown
Source)
at org.apache.derby.drda.NetworkServerControl.ping(Unknown Source)
at
org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerUp(NetworkServerTestSetup.java:546)
at
org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerStart(NetworkServerTestSetup.java:615)
at
org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:191)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.textui.TestRunner.doRun(TestRunner.java:121)
at junit.textui.TestRunner.start(TestRunner.java:185)
at junit.textui.TestRunner.main(TestRunner.java:143)
F.
testCreateClob used 16 ms .
testCreateBlob used 9 ms .
testConnectionIsValid used 674 ms
----------<hang>----------------------
The log shows the following
--------------------------------------
2009-04-20 16:41:07.264 GMT : Apache Derby Network Server - 10.5.1.1 - (764942)
started and ready to accept connections on port 1527
2009-04-20 16:41:10.618 GMT : Invalid reply from network server: Insufficient
data.
2009-04-20 16:41:10.618 GMT : Could not listen on port 1527 on host 127.0.0.1:
java.net.BindException: Address already in use: JVM_Bind
2009-04-20 16:41:12.416 GMT : Could not listen on port 1527 on host 127.0.0.1:
java.net.BindException: Address already in use: JVM_Bind
This hang occurred both times I ran suites.All and also when I ran jdbc4._Suite
alone , always on new test folders.
In the last instance, attempting to kill the hung test with
java org.apache.derby.drda.NetworkServerControl shutdown
also hung.
Javacore file attached.
> suites.All hang with message java.net.BindException: Address already in use:
> NET_Bind in derby.log
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-4053
> URL: https://issues.apache.org/jira/browse/DERBY-4053
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Attachments: derby-4053_repro_dont_commit_diff.txt, derby.log,
> javacore.20090211.123031.4000.0001.txt, suites.All.out
>
>
> Running suites.All with IBM 1.5 on 10.5.0.0 alpha - (743198) I got a hang
> in the test run. The last test to run successfully was
> xtestNestedSavepoints, but I am not sure exactly what test caused the hang.
> I took a thread dump which I will attach, which showed network server up and
> running but no ClientThread and a ping attempt blocked.
> This hang is very similar to the hang that was seen after the fix attempts
> for DERBY-1465 but that change was backed out so it is not related to that
> change. It could be that the change for DERBY-1465 just made this highly
> intermittent problem more likely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
