You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Shanthoosh Venkataraman (JIRA)" <ji...@apache.org> on 2017/04/07 21:22:41 UTC

[jira] [Created] (SAMZA-1196) Fix TestJmxReporter flaky tests

Shanthoosh Venkataraman created SAMZA-1196:
----------------------------------------------

             Summary: Fix TestJmxReporter flaky tests
                 Key: SAMZA-1196
                 URL: https://issues.apache.org/jira/browse/SAMZA-1196
             Project: Samza
          Issue Type: Bug
    Affects Versions: 0.13.0
            Reporter: Shanthoosh Venkataraman
             Fix For: 0.13.0


TestJmxReporter brings up an EmbeddedJmxServer and uses it to test the reporter behavior. However, due to failures in bringing up/connecting to JMX server, this fails intermittently. Here is the failure exception.
testJmxReporter FAILED
java.rmi.ConnectException: Connection refused to host: 115.98.154.104.bc.googleusercontent.com; nested exception is: 
java.net.ConnectException: Connection timed out (Connection timed out)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:130)
at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2430)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:308)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:229)
at org.apache.samza.metrics.reporter.TestJmxReporter.testJmxReporter(TestJmxReporter.scala:76)
Caused by:
java.net.ConnectException: Connection timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)


This will track effort required to fix this test.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)