ActiveMQ MQTT (QoS 1) doesn't republish messages when client not acknowledged the messages
I'm using ActiveMQ 5.10 as the MQTT Broker with one Java client to send messages in JMS and one C client to receive the messages. Here's the Java code snippet: MessageProducer producer = session.createProducer(new ActiveMQTopic("topic1")); TextMessage text = session.createTextMessage("test msg"); text.setIntProperty("ActiveMQ.MQTT.QoS",1); producer.send(text); After capturing the TCP packages, I confirmed the problem: If ActiveMQ sent out a message but didn't receive a PUBACK from the C client, ActiveMQ didn't resend the message. So the C client would never receive the message any more, event the message was under QoS 1 (at-least-once). How can I send the message with JMS (and/or configure ActiveMQ) to make QoS 1 truely work? Thanks a lot!
Where should I add the failover:tcp://host:port?
Does Apache Apollo have failover support?
Creating AMQ network of broker clusters on JBoss Fuse 6.2, without fabric
Could not refresh JMS Connection for destination 'queue://inventorydsDestination' - retrying in 5000 ms. Cause: AOP configuration seems to be invalid
ConcurrentConsumers not created using DefaultMessageListenerContainer but using maximumActiveSessionsPerConnection on PooledConnectionFactory
ActiveMQ messages getting stuck in networked broker setup
Difference between “Active Non-durable Subscibers” and “Active Subscribers” for a particular Topic
Negative count in ActiveMQ pending message
ActiveMQ inactivity timeout
Need Activemq MemoryUsage optimization - my queues are overflowing
ActiveMq customers cannot receive messages
Activemq not start in linux mint17
ActiveMQ Redelivery Police for a message
Identify connected ClientId's in ActiveMQ Network Brokers
Format ActiveMQ server like hdfs node format?
Does auto-acknowledge mean no-ack?