Using cxf 3.1.4 and WS-RM + persistence store with standard configuration (http://cxf.apache.org/docs/wsrmconfiguration.html), the last processed message ID in destination sequences are being lost after service restart.
Problem appears to be originating in RMTxStore.getDestinationSequences method, which restores list of open sequences from configured datasource. However, private field of DestinationSequence class "highNumberCompleted" is not initialized and its value is always 0 for every restored sequence. This is causing problem if delivery assurance is InOrder and ExactlyOnce/AtLeastOnce because all incomming messages with id > 1 are being postponed and wait for message 1, which may have already been processed before restart. Strangely, repeating processed messages correctly fails with "Message with number x in sequence xyz has already been delivered". Looks like a bug to me - or am I missing something? -- View this message in context: http://cxf.547215.n5.nabble.com/RMTxStore-getDestinationSequences-is-not-recovering-last-processed-messageId-tp5765307.html Sent from the cxf-user mailing list archive at Nabble.com.
