Hi HappyMan, You're welcome!
That's good to know -- I figured the InactivityMonitor was enabled, good to know that it was disabled. Enabling it will help I'm sure, you might need to tweak some of the timeout values, etc, but, good luck and keep us posted! -Justin On 10/21/19, 3:30 PM, "HappyMan" <[email protected]> wrote: Hi Justin, Thank you ver much for your reply. It helps me to think in a right way (I guess). Not only I adjusted ActiveMQ broker. I checked broker file ActiveMQ.xml again and find out that for mqtt transport connector was set parameter "transport.useInactivityMonitor=false". It means that checking if connection active or not was disabled... Tommorow I wil turn it on and I will add keepAlive parameter for MQTT client and I will set it 10 seconds. I hope it will work. Probably I think broker will close connection in 10 seconds when pingreq/pingresp won't be passed due to mobile internet will be off and connection on MQTT client will be lost. In that case I really hope that Active durable subscription will become Offline durable subscription. All in all, thank you, will try tommorow. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.
