But ideally it should be supported.
It may be possible that after switching broker to 5.10, broker or clients
can face some issues. In such scenerios, we revert broker back to 5.8. It
should be backward compatible.
Thanks,
Anuj
--
View this message in context:
On 07/06/2014 07:18 AM, khandelwalanuj wrote:
But ideally it should be supported.
It may be possible that after switching broker to 5.10, broker or clients
can face some issues. In such scenerios, we revert broker back to 5.8. It
should be backward compatible.
Thanks,
Anuj
--
View this
Patches happily accepted.
Sent from my pressure cooker.
On Jul 6, 2014, at 5:18, khandelwalanuj khandelwal.anu...@gmail.com wrote:
But ideally it should be supported.
It may be possible that after switching broker to 5.10, broker or clients
can face some issues. In such scenerios, we
After testing the scenario below with version 5.10.0, I've found that the
allowLinkStealing=true appears to work properly only for the *first*
reconnect; if the same MQTT client reconnects a second time (using the same
client-id) the previous connection is not closed and I get the following
Greetings
A friend recommended that a new Producer and Session should be created
for every message put on the queue. See below Is this correct?
put message on queue
try {
new ProducerTaskVoid() {
@Override
