activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Connection to activemq broker is lost within one second
Date Wed, 17 May 2017 13:01:03 GMT
I know very little about MQTT (Tim Bish knows that code much better, so
it's good that he's been involved in this thread so far), but I notice the
following in the log you attached:

11:31:43,850 DEBUG
(qtp764114829-245) Filled 10 bytes -
11:31:43,851 DEBUG [org.eclipse.jetty.websocket.common.Parser]
(qtp764114829-245) SERVER Parsing 10 bytes
11:31:43,852 DEBUG [org.eclipse.jetty.websocket.common.Parser]
(qtp764114829-245) SERVER OpCode CLOSE, fin=true rsv=...
11:31:43,853 DEBUG [org.eclipse.jetty.websocket.common.Parser]
(qtp764114829-245) SERVER Payload Length: 4 -

That block looks to me like the client requests that the connection be
closed, and the broker does as requested. I know you've said that your
client is not closing the connection (based primarily on the behavior
you see when connected to a non-ActiveMQ broker *using a different
underlying transport*), but I think it's time to re-evaluate that
assumption you've been making up to this point.

(The other) Tim

On May 17, 2017 4:28 AM, "aragoubi" <> wrote:

I upgraded to activemq 5.14.3, and I changed log level to debug.
Client still loosing connection just 1 second after connection.
Here is my server.log file :
server.log <>

View this message in context: http://activemq.2283324.n4.
Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message