i'm using the 5.8.0-snapshot, my setting:

<transportConnector name="mqtt"
uri="mqtt://113.31.65.60:1883?wireFormat.maxInactivityDuration=0"/>

And i got:

2012-10-22 16:10:45,674 | DEBUG | SampleJavaV3_subscribe MQTT Connection
using heart beat of  60 secs |
org.apache.activemq.transport.mqtt.MQTTProtocolConverter | ActiveMQ
Transport: tcp:///124.127.108.134:7442@1883
2012-10-22 16:10:45,699 | DEBUG | MQTT Client  connected. |
org.apache.activemq.transport.mqtt.MQTTProtocolConverter | ActiveMQ
Transport: tcp:///124.127.108.134:7442@1883
2012-10-22 16:12:45,674 | DEBUG | 60000 ms elapsed since last read check. |
org.apache.activemq.transport.mqtt.MQTTInactivityMonitor | InactivityMonitor
ReadCheck
2012-10-22 16:12:45,709 | DEBUG | Sent Ping Response to  |
org.apache.activemq.transport.mqtt.MQTTProtocolConverter | ActiveMQ
Transport: tcp:///124.127.108.134:7442@1883
2012-10-22 16:13:45,675 | DEBUG | 60001 ms elapsed since last read check. |
org.apache.activemq.transport.mqtt.MQTTInactivityMonitor | InactivityMonitor
ReadCheck
2012-10-22 16:14:45,675 | DEBUG | 60000 ms elapsed since last read check. |
org.apache.activemq.transport.mqtt.MQTTInactivityMonitor | InactivityMonitor
ReadCheck
2012-10-22 16:14:45,675 | DEBUG | No message received since last read check
for tcp:///124.127.108.134:7442@1883! Throwing InactivityIOException. |
org.apache.activemq.transport.mqtt.MQTTInactivityMonitor | InactivityMonitor
ReadCheck
2012-10-22 16:14:45,677 | WARN  | Transport Connection to:
tcp://124.127.108.134:7442 failed:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>60000) long: tcp://124.127.108.134:7442 |
org.apache.activemq.broker.TransportConnection.Transport |
MQTTInactivityMonitor Async Task:
java.util.concurrent.ThreadPoolExecutor$Worker@6e659812[State = 0, empty
queue]



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/MQTT-Impossible-to-disable-InactivityMonitor-tp4657945p4658032.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to