On Mon, May 10, 2010 at 3:53 AM, jid1jid1 wrote:
>
> Apologies for not raising an issue with jira (need time to login and as
> always running for deadlines. I have attached a draft Unit test that
> basically shows that a deadlock will occur if one message listener does not
> return (ie. a MessageL
>> If the queue is empty, everything works as expected.
>>
>> Seems like a bug to me. Has anyone experienced this before?
>>
>> Many thanks
>> --
>> View this message in context:
>> http://old.nabble.com/ActiveMQ-problem-with-closing-a-con
On Fri, May 7, 2010 at 9:29 AM, jid1jid1 wrote:
>
> Hi,
>
> I have the following setup:
> JMSClient - ActiveMQ 5.3.1
> JMSServer - ActiveMQ 5.3.0
>
> I create a QueueConnection-> QueueSession -> MessageConsumer
> I set my messageListener on the MessageConsumer and use conn.start() to
> flush
>
> I
as expected.
>
> Seems like a bug to me. Has anyone experienced this before?
>
> Many thanks
> --
> View this message in context:
> http://old.nabble.com/ActiveMQ-problem-with-closing-a-connection-that-has-a-MessageListener-attached-tp28487625p28487625.html
> Sent
stener or even
just CLOSE the connection, I get a deadlock.
If the queue is empty, everything works as expected.
Seems like a bug to me. Has anyone experienced this before?
Many thanks
--
View this message in context:
http://old.nabble.com/ActiveMQ-problem-with-closing-a-connection-that