activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro Marques (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-4338) MQTTSSLTest has multiple test cases that fail frequently
Date Wed, 20 Mar 2013 14:27:15 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607508#comment-13607508
] 

Pedro Marques edited comment on AMQ-4338 at 3/20/13 2:26 PM:
-------------------------------------------------------------

I was testing the system with fusesource client... My code is basically this:
{code}
	MQTT mqtt = new MQTT();
	mqtt.setHost(url);
	mqtt.setUserName(user);
	mqtt.setPassword(password);

	BlockingConnection connection = mqtt.blockingConnection();
	connection.connect();
{code}
I think the problem I was having was the one described in this issue because the call hangs
on "connection.connect()". The code works perfectly when run on the same machine as the server
or when the url is not ssl based.




                
      was (Author: pmarques):
    I was testing the system with fusesource client... My code is basically this:

	MQTT mqtt = new MQTT();
	mqtt.setHost(url);
	mqtt.setUserName(user);
	mqtt.setPassword(password);

	BlockingConnection connection = mqtt.blockingConnection();
	connection.connect();

I figured the problem I was having was this because the call blocks on "connection.connect()".
The code works perfectly when run on the same machine as the server or when the url is not
ssl based.




                  
> 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 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(LockSupport.java:186)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(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(BlockingConnection.java:49)
>         at org.apache.activemq.transport.mqtt.FuseMQQTTClientProvider.connect(FuseMQQTTClientProvider.java:39)
>         at org.apache.activemq.transport.mqtt.MQTTSSLTest.initializeConnection(MQTTSSLTest.java:60)
> 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: http://www.atlassian.com/software/jira

Mime
View raw message