Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 21 Feb 2013 20:28:12 +0000 (UTC)
From: "Kevin Earls (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12633271.1361393545935.319347.1361478492881@arcas>
In-Reply-To: <JIRA.12633271.1361393545935@arcas>
References: <JIRA.12633271.1361393545935@arcas>
Subject: [jira] [Updated] (AMQ-4338) MQTTSSLTest has multiple test cases
 that fail frequently
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/AMQ-4338?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Earls updated AMQ-4338:
-----------------------------

    Attachment: AMQ-4338A.patch

This patch bumps up the timeouts from the previous patch.  I had set them t=
o 30 seconds, but that's not enough on some slow nodes.
               =20
> MQTTSSLTest has multiple test cases that fail frequently
> --------------------------------------------------------
>
>                 Key: AMQ-4338
>                 URL: https://issues.apache.org/jira/browse/AMQ-4338
>             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 testSendAndRecei=
veExactlyOnce, testSendAndReceiveLargeMessages, testSendAndReceiveMQTT, tes=
tSendAtLeastOnceReceiveAtMostOnce, testSendAtLeastOnceReceiveExactlyOnce, t=
estSendJMSReceiveMQTT, testSendMQTTReceiveJMS) which fail fairly frequently=
 because of a hang on the provider.connect() call in initializeConnection()=
 as shown in the stacktrace below.=20
> Another problem with this test is it was giving a misleading error when r=
un under Hudson, showing that the test that followed it (MQTTTest) was fail=
ing instead.  I think this was because of the way it was using AutoFailTest=
Support.  I will attach a patch which removes that and uses timeouts on @Te=
st annotations instead.
> testSendAndReceiveLargeMessages(org.apache.activemq.transport.mqtt.MQTTSS=
LTest)  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(LockSupport.java:1=
86)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndC=
heckInterrupt(AbstractQueuedSynchronizer.java:834)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquir=
eSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireS=
haredInterruptibly(AbstractQueuedSynchronizer.java:1303)
>         at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:=
236)
>         at org.fusesource.mqtt.client.Promise.await(Promise.java:88)
>         at org.fusesource.mqtt.client.BlockingConnection.connect(Blocking=
Connection.java:49)
>         at org.apache.activemq.transport.mqtt.FuseMQQTTClientProvider.con=
nect(FuseMQQTTClientProvider.java:39)
>         at org.apache.activemq.transport.mqtt.MQTTSSLTest.initializeConne=
ction(MQTTSSLTest.java:60)
> Results :
> Tests in error:
>   MQTTSSLTest>AbstractMQTTTest.testSendAndReceiveLargeMessages:247->initi=
alizeConnection:60 =C2=BB

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira