Could you simulate your error condition in a junit test and post it
for us to review? I agree the broker should be more isolated.
On Mon, May 12, 2008 at 4:33 PM, jgunz <[EMAIL PROTECTED]> wrote:
>
> We identified what was causing the problem. One of our consumers had an
> uncaught exception that
We identified what was causing the problem. One of our consumers had an
uncaught exception that was occasionally thrown in the MessageListener
thread. By simply preventing this exception we no longer see the broker lock
ups.
Is this expected consumer behavior? It seems that the broker/server shou
Daryl Richter-3 wrote:
>
> Do you open and close multiple sessions within the same consumer thread?
>
> We have seen that this can very reliably cause the broker to lock up.
>
> It is best to open a single session per thread and close all the way out
> when done consuming.
>
Is it wrong to
jgunz wrote:
I have been using ActiveMQ 4.1.1 for awhile in a production product and
recently we have been seeing occasional lock-ups/freezes that go away when
we restart ActiveMQ. From our clients or from the ActiveMQ log we cannot see
that there is a problem, we just stop seeing message through
