In order to have the right behavior we need an ExecutorService (or
another thread pool implementation) with an execute method that blocks
until a worker thread becomes available. I don't see how to achieve
this with java.util.concurrent. Maybe somebody more familiar with this
can give a hint?
Note that even if we can change the worker pool behavior in this way,
we still need to change the acknowledgement behavior: otherwise there
is still the risk of loosing the message that is waiting for a thread
to become available.
Andreas,
Here the issue is having an unreliable queue in the middle. I thought it
was as simple as adding persistence to this queue itself. I am not aware
how the internals really work. But according to your issue that is a
feasible solution?
Danushka
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
