Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Fri, 29 Nov 2013 17:00:09 -0800 (PST)
From: Brian Reinhold <brianreinhold@lampreynetworks.com>
To: users@activemq.apache.org
Message-ID: <1385773209176-4674961.post@n4.nabble.com>
Subject: Apollo MQTT server ignoring keepalive timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have set the WILL message to send a LOST payload on a status topic which I
have defined (QoS = 2). The keep alive time is set to 20 seconds. According
to the MQTT spec

The Will message defines that a message is published on behalf of the client
by the
server when either an I/O error is encountered by the server during
communication
with the client, or the client fails to communicate within the Keep Alive
timer schedule

so I would expect that after 20 seconds I would get the LOST message
published on the status topic on the server side (the apollo MQTT broker is
embedded in a server). But nothing happens.

If I publish the message in code it is properly received on the correct
topic. Is the problem that the client application is on the same machine as
the server and the broker (client and server are using TLS with client
authentication as is the client and the broker)? All other aspects of
connect and setup of the broker appear to be working correctly (I can
publish and receive messages 'remotely' if I have subscribed).


--
View this message in context: http://activemq.2283324.n4.nabble.com/Apollo-MQTT-server-ignoring-keepalive-timeout-tp4674961.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.