Hi Steve, it's been quite a while.
We are experiencing the bug detailed below.
Do you have a specific patch for this for 1.2.1, or is 1.3.0 stable enough
for production.

This could be related to a open bug about the timer events not being
processed in an acceptor while it's disconnected (QFJ-218). This would
cause the logout with the old sequence number to be sent the first time
someone connects. Subsequent connections should be ok and should use the
new session's sequence numbers. If we can complete the 1.3 release soon,
I'll have the fix in there. Otherwise, I'll patch 1.2.1 and release a
new version of that branch.

A temporary workaround is to call reset manually on the message
store before the new session start time.

Regards,

Steve