Dead lock while multi-consumers listening

[kidfruit <ki...@gmail.com>]

My problem is having deadlock when listening activemq channel. And no
exception or any notify, just stop there.

The detail is:

Use c# and nms library.

Create a console program, then create a work thread in main thread. Main
thread just stop for monitor state, all work is in work thread.

Create many consumers, share one connection, each consumer use its own
session. Then each consumer use Listener event to listen data, that means
there are many listen event thread is working. The data will print to
console.

At begining, it works. But after some time, I found that no new data print
to console. Debug by attach the process, all thread is doing nothing, and no
error occur. It seems like causing a deadlock. But I don't know how to check
the problem. I tested exception events of connection, no callback at all. 

Is there any suggestion to check the problem?



--
View this message in context: http://activemq.2283324.n4.nabble.com/Dead-lock-while-multi-consumers-listening-tp4693338.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: Dead lock while multi-consumers listening

[Thiago Kronig <th...@gmail.com>]

Take a thread dump a post it. That way will be easier to spot the problem.

Em sex, 20 de mar de 2015 12:08, kidfruit <ki...@gmail.com> escreveu:

> My problem is having deadlock when listening activemq channel. And no
> exception or any notify, just stop there.
>
> The detail is:
>
> Use c# and nms library.
>
> Create a console program, then create a work thread in main thread. Main
> thread just stop for monitor state, all work is in work thread.
>
> Create many consumers, share one connection, each consumer use its own
> session. Then each consumer use Listener event to listen data, that means
> there are many listen event thread is working. The data will print to
> console.
>
> At begining, it works. But after some time, I found that no new data print
> to console. Debug by attach the process, all thread is doing nothing, and
> no
> error occur. It seems like causing a deadlock. But I don't know how to
> check
> the problem. I tested exception events of connection, no callback at all.
>
> Is there any suggestion to check the problem?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Dead-lock-while-multi-consumers-listening-tp4693338.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>