|
From: Steve B. <st...@te...> - 2007-08-09 00:18:54
|
Anshu, 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 |