Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.14.0
-
Fix Version/s: None
-
Component/s: camel-jms
-
Labels:None
-
Environment:
All
-
Estimated Complexity:Unknown
Description
When used with a PooledConnectionFactory, a Camel Route that consumes via JMS from an ActiveMQ endpoint will read one extra message and simply discard it after it has completed suspension, if that message is sent within a second of suspension being completed.
See attached test case.
As far as I can tell this is because nothing interrupts the taskExecutor on DefaultMessageListenerContainer when a route is suspended.
Expected behaviour - once a route is suspended, any messages sent to the queue from which it consumes should remain on that queue.