activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-4338) MQTTSSLTest has multiple test cases that fail frequently
Date Tue, 26 Feb 2013 18:24:13 GMT


Timothy Bish commented on AMQ-4338:

I did some profiling and testing today.  So far I couldn't find any real issues.  It seems
that in the case of these tests the QOS setting just makes things ungodly slow due to all
the back and forth acking that's going on.  I guess its possible there's something amiss in
the FuseSource MQTT client library but so far I haven't found anything.
> MQTTSSLTest has multiple test cases that fail frequently
> --------------------------------------------------------
>                 Key: AMQ-4338
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>            Reporter: Kevin Earls
>            Priority: Minor
>         Attachments: AMQ-4338A.patch, AMQ-4338.patch
> MQTTSSLTest has multiple different test cases (including testSendAndReceiveExactlyOnce,
testSendAndReceiveLargeMessages, testSendAndReceiveMQTT, testSendAtLeastOnceReceiveAtMostOnce,
testSendAtLeastOnceReceiveExactlyOnce, testSendJMSReceiveMQTT, testSendMQTTReceiveJMS) which
fail fairly frequently because of a hang on the provider.connect() call in initializeConnection()
as shown in the stacktrace below. 
> Another problem with this test is it was giving a misleading error when run under Hudson,
showing that the test that followed it (MQTTTest) was failing instead.  I think this was because
of the way it was using AutoFailTestSupport.  I will attach a patch which removes that and
uses timeouts on @Test annotations instead.
> testSendAndReceiveLargeMessages(org.apache.activemq.transport.mqtt.MQTTSSLTest)  Time
elapsed: 30.004 sec  <<< ERROR!
> java.lang.Exception: test timed out after 30000 milliseconds
>         at sun.misc.Unsafe.park(Native Method)
>         at java.util.concurrent.locks.LockSupport.park(
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(
>         at java.util.concurrent.CountDownLatch.await(
>         at org.fusesource.mqtt.client.Promise.await(
>         at org.fusesource.mqtt.client.BlockingConnection.connect(
>         at org.apache.activemq.transport.mqtt.FuseMQQTTClientProvider.connect(
>         at org.apache.activemq.transport.mqtt.MQTTSSLTest.initializeConnection(
> Results :
> Tests in error:
>   MQTTSSLTest>AbstractMQTTTest.testSendAndReceiveLargeMessages:247->initializeConnection:60

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

View raw message