we're running ActiveMQ 5.8 and have an issue with message dispatching on
consumer side
actually, the onMessage method of a MessageListener is not called
debugging this reveals that this is due to the PooledTaskRunner being used
during async dispatching returns in its wakeup method without any action
the runTask method is not executed
the same behavior as stated in
https://issues.apache.org/jira/browse/AMQ-5215 (Unresolved)
I was thinking about a fix, but as PooledTaskRunner is a very central class
it would be nice to get some advice on a potential fix
during PooledTaskRunner.wakeup() is must be ensured that there is an active
thread executing runTask() before leaving (queued=true)
consumer side
actually, the onMessage method of a MessageListener is not called
debugging this reveals that this is due to the PooledTaskRunner being used
during async dispatching returns in its wakeup method without any action
the runTask method is not executed
the same behavior as stated in
https://issues.apache.org/jira/browse/AMQ-5215 (Unresolved)
I was thinking about a fix, but as PooledTaskRunner is a very central class
it would be nice to get some advice on a potential fix
during PooledTaskRunner.wakeup() is must be ensured that there is an active
thread executing runTask() before leaving (queued=true)