Arunava Bhattacharya created AMQ-5532: -----------------------------------------
Summary: ActiveMQ 5.9-SUBSCRIBER does not receive message from broker after reconneting Key: AMQ-5532 URL: https://issues.apache.org/jira/browse/AMQ-5532 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.9.1, 5.9.0 Environment: OS-Solaris JRE1.6 Reporter: Arunava Bhattacharya Fix For: NEEDS_REVIEW Hi, I am currently facing a problem while using Active MQ 5.9 as broker. My System set up is as follows: System Context ------------------------- PUB(JMS Client)<--------->ACTIVE MQ BROKER(5.9)<------>SUB(MQTT Client) Scenario ------------- -10 messages are scheduled at publisher end and fired -SUBSCRIBER is disconnected after receiving 1 message -SUBSCRIBER is reconnected again -SUBSCRIBER does not receive remaining messages. SUBSCRIBER ------------------ - This is a durable subscriber. -Connects using cleanSession Flag as false -Subscribes using Requested QoS=2 -Keep Alive is 30sec Observation ------------------------ -Messages from JMS client are converted MQTT with QoS=0 at broker side - Messages are lost incase they are scheduled in blulk from the PUBLISHER end only. -For instant single message this problem does not occur. Questions ------------------------- -Does this mean that delivery is not assured? -How setting the persistence flag at JMS prodcuer end is translated to a MQTT message ? In general what is the logic to translate a JMS message to a MQTT message considering QoS? -Are the messages stored in some in memory DB? and retried ? -Is there a fix regarding this issue available in version 5.10 ? I see lot of improvements in 5.10 related to MQTT -- This message was sent by Atlassian JIRA (v6.3.4#6332)