Seeing inflight messages that are not consumed when jmsPriority is enabled and have intermittent durable consumer

With reconnecting durable subs or with small prefetch, out of order priority messages and missing messages can occur. Issues with the kahaDB topic store, message delete and ordered cursor sync and replay.

Topic store sd.orderIndex need an exclusive lock and replay from the last ack needs to take ordered cursors into account. Batch replay also needs to maintain ordered cursor state between batches.

JDBC store also has some issues in the batch regard.