activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Mielke (Updated) (JIRA)" <>
Subject [jira] [Updated] (AMQ-3754) intermittent failure of org.apache.activemq.transport.vm.VmTransportNetworkBrokerTest
Date Fri, 02 Mar 2012 11:50:56 GMT


Torsten Mielke updated AMQ-3754:

    Attachment: AMQ-3754.patch

Attaching a fix which updates the JUnit test. 
Initially the test was simply taking the thread count at the end of the test run and comparing
it against the thread count in the beginning. The test failed if these counts did not match.

The new version now takes a list of all threads under the same main thread group at the end
of the test run and removes any daemon threads from that list. 
This will filter out any additional threads created by the JVM. 
Then the count of that thread list is taken and compared against the initial thread count.
> intermittent failure of org.apache.activemq.transport.vm.VmTransportNetworkBrokerTest
> -------------------------------------------------------------------------------------
>                 Key: AMQ-3754
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>            Reporter: Torsten Mielke
>            Assignee: Torsten Mielke
>              Labels: test, test-fail
>             Fix For: 5.6.0
>         Attachments: AMQ-3754.patch
> The JUnit test org.apache.activemq.transport.vm.VmTransportNetworkBrokerTest fails most
of the time on a Mac OSX machine. 
> The reason for the failure is that the test assumes the JVM itself will not create any
additional threads at runtime. This however is a false assumption as on Mac OSX a daemon thread
called "Poller SunPKCS11-Darwin" is created at some later point in time (after the test got
kicked off already) under the main thread group. 
> This extra but JVM internal thread makes the test fail on Mac OSX right now.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message