I have now run 4 full runs of the complete junit suite with following
results in my environment:
10 second timeout - 23 timeout errors in the JMX suites
10 second timeout - ~10 timeout errors in the JMX suites
300 second timeout - all tests pass (except for reported replication
failures).
60 second timeout - all tests pass (except for reported replication
failures).
I have also run 50 sets of just the JMX with the 10 second timeout and
all those pass, so I assume the problem is related to some other test
somehow affecting the JVX tests.
All the above tests are run on a laptop, connected to a VPN network,
both hardware and software firewalls and a dsl line. Would not think
any of that really mattered for a connection to network server on same
machine, but I have no idea.
I am going to try another 10 second run and then follow that to see how
low I can get the timeout before getting errors.
I wonder if there is a error handling bug that is missing the timeout
from network server startup for the JMX tests?
Daniel John Debrunner (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576573#action_12576573 ]
Daniel John Debrunner commented on DERBY-3515:
----------------------------------------------
Not sure what to say. Since the jmx connections are made after the
NetworkServerTestSetup has sun its setUp method that implies to me that the
NetworkServerTestSetup .setUp() always succeeded and thus the network server
timeout was never exceeded. If the server failed to come up in less than 10
seconds you would see a failure of timeout trying to connect to the network
server and not see any jmx connection attempts.
I try running the tests over the weekend as well. Could it have been a one-off
failure in your environment?
23 timeouts encountered while running management junit suite as part of full
nightly runs.
------------------------------------------------------------------------------------------
Key: DERBY-3515
URL: https://issues.apache.org/jira/browse/DERBY-3515
Project: Derby
Issue Type: Bug
Components: Regression Test Failure
Affects Versions: 10.4.0.0
Environment: windows XP, laptop, ibm15
Reporter: Mike Matrigali
Attachments: summary.out
While running full nightly test suite on a classes,SANE build got 23 failures
in management test suite as follows. Tried again in same codeline
just running the management test suite and it worked 50 times in a row. Maybe
issue is similar to DERBY-3514, where a previous test is leaving
a bad state and now that timeout has been reduced again to where it was known
to cause nightly test failures in some environments those issues
are resurfacing. I am trying another full suite run to see if it reproduces in
my environment, if others are seeing this issue, please add a comment.
I will attach full log of errors, but here is the first few:
There were 23 errors:
1)
testDerbyRegisteredMBeansSimpleInfo(org.apache.derbyTesting.functionTests.tests.management.JMXTest)java.rmi.ConnectIOException:
Exception creating
connection to: 192.168.0.188; nested exception is:
java.net.SocketException: Operation timed out: connect:could be due to
invalid address
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:603)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:204)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:109)
at
javax.management.remote.rmi.RMIServerImpl_Stub.newClient(RMIServerImpl_Stub.java:52)
at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2244)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:286)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:263)
at
org.apache.derbyTesting.functionTests.tests.management.RemoteConnectionGetter.getMBeanServerConnection(RemoteConnectionGetter.java:49)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getMBeanServerConnection(MBeanTest.java:177)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getApplicationManagementMBean(MBeanTest.java:252)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.enableManagement(MBeanTest.java:201)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.setUp(MBeanTest.java:155)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:101)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.net.SocketException: Operation timed out: connect:could be due
to invalid address
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:372)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:233)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:220)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)
at java.net.Socket.connect(Socket.java:541)
at java.net.Socket.connect(Socket.java:491)
at java.net.Socket.<init>(Socket.java:399)
at java.net.Socket.<init>(Socket.java:208)
at
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:41)
at
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:145)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:585)
2)
testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)java.rmi.ConnectIOException:
Exce
ption creating connection to: 192.168.0.188; nested exception is:
java.net.SocketException: Operation timed out: connect:could be due to
invalid address
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:603)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:204)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:109)
at
javax.management.remote.rmi.RMIServerImpl_Stub.newClient(RMIServerImpl_Stub.java:52)
at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2244)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:286)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:263)
at
org.apache.derbyTesting.functionTests.tests.management.RemoteConnectionGetter.getMBeanServerConnection(RemoteConnectionGetter.java:49)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getMBeanServerConnection(MBeanTest.java:177)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getApplicationManagementMBean(MBeanTest.java:252)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.enableManagement(MBeanTest.java:201)
at
org.apache.derbyTesting.functionTests.tests.management.MBeanTest.setUp(MBeanTest.java:155)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:101)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.net.SocketException: Operation timed out: connect:could be due
to invalid address
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:372)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:233)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:220)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)
at java.net.Socket.connect(Socket.java:541)
at java.net.Socket.connect(Socket.java:491)
at java.net.Socket.<init>(Socket.java:399)
at java.net.Socket.<init>(Socket.java:208)
at
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:41)
at
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:145)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:585)
... 49 more
