We have a system where we are receiving messages from a Topic using durable subscribers. We have two durable subscribers pulling messages off the topic 250 messages at a time and then call session.commit(). We have found an issue where when one of the subscribers goes down (connection is terminated) after receiving 250 messages but before calling session.commit(). When this subscriber is restarted the messages which would have been rolled back (i.e. the last 250) are delivered in the reverse order. For example the subscribers both receive messages with ids 1 to 250 in order before the restart, then after the restart the subscriber that was restarted receives the messages with Ids 1-250 in the order 250,249,248,...,3,2,1.
Has anyone else experienced this issue and if so is there anything I can do to overcome this? (I have found this on both version 5.3.0 and 5.3.2) Thanks Colin This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies within the Detica Limited group of companies. Detica Limited is registered in England under No: 1337451. Registered offices: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.
