[
https://issues.apache.org/jira/browse/DERBY-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004754#comment-13004754
]
Kathey Marsden commented on DERBY-4852:
---------------------------------------
When this problem occurs in the test trace output we see:
testFailedStreamInsertBinaryRollbackOnError used 94 ms .
testFailedStreamInsertBinaryAutoCommitRollbackOnError used 140 ms .
test_basic used 15 ms .
test_basic used 31 ms .
test_basic used 32 ms .
test_basic used 32 ms .
testDerbyRegisteredMBeansSimpleInfo used 16 ms .
testDerbyRegisteredMBeansSimpleInfo used 1484 ms
ESTART-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port
already in use: 1530; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
Exception in thread "jlmAgent" java.lang.Error: snmp agent failed to launch
at com.ibm.misc.SystemIntialization$3.run(SystemIntialization.java:190)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.misc.SystemIntialization$3.run(SystemIntialization.java:187)
Caused by: java.lang.RuntimeException: Exception thrown by the agent
at sun.management.Agent.error(Agent.java:331)
at sun.management.Agent.error(Agent.java:322)
at sun.management.Agent.startAgent(Agent.java:171)
at sun.management.Agent.startAgent(Agent.java:267)
... 5 more
END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:
testStartStopManagementFromApplication used 0 ms .
testStartStopManagementFromApplication used 1390 ms
ESTART-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port
already in use: 1530; nested exception is: ....
and then repeated for subsequent network server runs of the test.
I am not sure if the embedded version of the test uses remote jmx connections
or local, but I am guessing local as all the embedded ones pass but not
network server which is trying to use the remote port 1530. This is the first
JXM network server test to run, so I am not sure what is binding up the port.
Note when I have seen these failures due to the firewall issue I do not
remember seeing the ESTART-SPAWNED error. In that case I think the server
starts fine, but just the client can't connect, so I think this output is a
good indicator of the two different types of failures.
> Lots of failures with Connection Refused, starting with
> JMXtest.testDerbyRegisteredMBeansSimpleInfo on 10.6.2.3(1022806) codeline
> while running Junit suite with ibm16 on windows machine
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4852
> URL: https://issues.apache.org/jira/browse/DERBY-4852
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3
> Reporter: Mamta A. Satoor
> Assignee: Kathey Marsden
> Labels: derby_triage10_8
> Attachments: 1022806-suites.All_diff.txt
>
>
> Last night's run of Junit with ibm16 on 10.6.2.3(1022806) codeline had 50
> failures which all seem to be related to not being able to open a connection
> to the localhost. The link to that run can be found at
> http://people.apache.org/~myrnavl/derby_test_results/v10_6/windows/testSummary-1022806.html
> I will also attach the result of the run to this jira.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
