ProducerFlowControlTest highlights that the test may may not always wait for 
shutdown the JMX interface.
--------------------------------------------------------------------------------------------------------

                 Key: QPID-2394
                 URL: https://issues.apache.org/jira/browse/QPID-2394
             Project: Qpid
          Issue Type: Bug
          Components: Java Tests
    Affects Versions: 0.6
            Reporter: Martin Ritchie


Below is the stack trace from the error failure.

When running the InVM tests we cleanly close the InVM broker. However, this is 
not representative of a normal clean broker shutdown as the VM does not exit. 
The exiting VM would not be held up if the JMX threads were not stopped. The 
fact that the tests do not always fail suggests that the JMS interface is 
closing but sometimes takes a little longer. Additional checks to ensure it has 
stopped could be performed to prevent these types of test failure

Testcase: testSendTimeout took 0.045 sec
        Caused an ERROR
Port already in use: 3328; nested exception is: 
        java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 3328; nested exception 
is: 
        java.net.BindException: Address already in use
        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
        at 
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
        at 
sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68)
        at 
java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222)
        at 
org.apache.qpid.server.management.JMXManagedObjectRegistry.start(JMXManagedObjectRegistry.java:228)
        at 
org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry.initialise(ConfigurationFileApplicationRegistry.java:78)
        at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:105)
        at 
org.apache.qpid.test.utils.QpidTestCase.startBroker(QpidTestCase.java:457)
        at 
org.apache.qpid.test.utils.QpidTestCase.startBroker(QpidTestCase.java:394)
        at org.apache.qpid.test.utils.QpidTestCase.setUp(QpidTestCase.java:284)
        at 
org.apache.qpid.server.logging.AbstractTestLogging.setUp(AbstractTestLogging.java:41)
        at 
org.apache.qpid.server.queue.ProducerFlowControlTest.setUp(ProducerFlowControlTest.java:69)
        at 
org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:239)
        at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:298)
Caused by: java.net.BindException: Address already in use
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at java.net.ServerSocket.<init>(ServerSocket.java:97)
        at 
org.apache.qpid.server.management.JMXManagedObjectRegistry$CustomRMIServerSocketFactory$NoLocalAddressServerSocket.<init>(JMXManagedObjectRegistry.java:318)
        at 
org.apache.qpid.server.management.JMXManagedObjectRegistry$CustomRMIServerSocketFactory.createServerSocket(JMXManagedObjectRegistry.java:311)
        at 
sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to