Comment 6 for bug 890724

Hi Roger,

I tested the last version=>0.13.9. The bug has been fixed. :)

Thanks a lot!
David

2011/11/16 Roger Light <email address hidden>

> Thanks for the offer, but I think it's already fixed. If you're happy
> compiling the code yourself, you can give the fix a try at this link:
> https://bitbucket.org/oojah/mosquitto/src/885e23ff76c4 There is a "get
> source" link on the right hand side of the page.
>
> If you could confirm that it's fixed for you that'd be very helpful.
>
> ** Changed in: mosquitto
> Status: Confirmed => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/890724
>
> Title:
> Server does't push Qos 1 messages to client after client reconnect
>
> Status in mosquitto: an mqtt message broker:
> Fix Committed
>
> Bug description:
> I'm using sever version 0.13 and wmqtt.jar library. Below is the
> re-produce steps:
> 1) client connect to server and subscribe one topic using
> clean_state=false and Qos=1
> 2) Make the client lost the connection until the server side
> disconnecting by timeout.
> 3) publish some messages to the topic in the step 1).
> 4) Re-connect the client to the server with the same subscribe in step 1)
> 5) Client should receive the messages in the step 3) immediately after
> the connection. In fact server will not send the missed messages to the
> re-connected client except publishing a new message on this topic.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mosquitto/+bug/890724/+subscriptions
>