activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Jarvis (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-3898) Server restart required after accessing via MQTT
Date Mon, 25 Jun 2012 14:18:42 GMT
Martin Jarvis created AMQ-3898:
----------------------------------

             Summary: Server restart required after accessing via MQTT
                 Key: AMQ-3898
                 URL: https://issues.apache.org/jira/browse/AMQ-3898
             Project: ActiveMQ
          Issue Type: Bug
          Components: MQTT
    Affects Versions: 5.6.0
         Environment: MacOS Lion, java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-11M3635)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
            Reporter: Martin Jarvis
         Attachments: activemq.xml

I am using the Paho sample client (org.eclipse.paho.sample.mqttv3app.Sample) to access the
MQTT server in ActiveMQ. After an initial successful connection,  I receive the following
error:
Broker unavailable (3)
	at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
	at org.eclipse.paho.client.mqttv3.internal.ClientComms.connect(ClientComms.java:172)
	at org.eclipse.paho.client.mqttv3.MqttClient.connect(MqttClient.java:339)
	at org.eclipse.paho.client.mqttv3.MqttClient.connect(MqttClient.java:308)
	at org.eclipse.paho.sample.mqttv3app.Sample.publish(Sample.java:185)
	at org.eclipse.paho.sample.mqttv3app.Sample.main(Sample.java:124)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)

To reconnect I have to restart the ActiveMQ server.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message