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
[org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection]
(qtp764114829-245) Filled 10 bytes -
DirectByteBuffer@2c84d353[p=0,l=10,c=4096,r=10]={<<<\x88\x84<\x1b6\x11\r+\x06!>>>MQTT\x04\xC0\x00\x1e\x00\nJavaSam...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
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 -
Parser@25d94d80[ExtensionStack,s=PAYLOAD_LEN,c=0,len=4,f=CLOSE[len=0,fin=true,rsv=...,masked=true],p=WebSocketPolicy@5d6f21e9[behavior=SERVER,maxTextMessageSize=65536,maxTextMessageBufferSize=32768,maxBinaryMessageSize=65536,maxBinaryMessageBufferSize=32768,asyncWriteTimeout=60000,idleTimeout=300000,inputBufferSize=4096]]
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" <aymen....@gmail.com> 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 <http://activemq.2283324.n4.nabble.com/file/n4726230/server.log>
--
View this message in context: http://activemq.2283324.n4.
nabble.com/Connection-to-activemq-broker-is-lost-within-one-second-
tp4726204p4726230.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
