Major Description
We think we've found an issue with durable topic subscriptions and message selectors.
The attached application sends messages with an int property i with values 0..19 to a topic. We also have a durable subscription to the topic, selecting messages for which i%2=0. After sending the messages, the connection is started, allowing the consumer to receive the messages we've published that match the selection criterion. The second and every subsequent time we run the application, we see the following:
message.i = 19
message.i = 0
message.i = 2
message.i = 4
message.i = 6
message.i = 8
message.i = 10
message.i = 12
message.i = 14
message.i = 16
message.i = 18
message.i = 19 does not match the message selector criterion but it reaches our message handler anyway.
Tested with ActiveMQ from trunk, revision 486090.