You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by bgm_fr <bg...@hotmail.com> on 2007/03/27 21:17:01 UTC

Queue message reception failure

Hi all,

  There's something weird happening with my application. 

My app consists in two queues : one for command and one for notification. So
I got 2 producer/consumer couples.
When everything (firstApp activeMq secondApp) is on the same computer,
everything works fine. Troubles happen when we try to put the fisrt app and
secondApp on two different computers. One way works fine (from firstApp to
secondApp) but not the other way (secondApp to firstApp).

What is really weird here is that when watching through jmx consol, we can
see that the message from second to first is sent, that a consumer is
listening on it (the one from firstApp), even that there was a dispatch to
this consumer but still the consumer.receive(timeOut) returns null and the
queue is not decreased.
  
Another detail, if we put firstApp and secondApp on the same computer and
activeMQ on another computer it works fine. 

I am becoming a bit crazy with this, has anyone got an idea ?

Thanks in advance,

-- 
View this message in context: http://www.nabble.com/Queue-message-reception-failure-tf3475041s2354.html#a9699184
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: Queue message reception failure

Posted by James Strachan <ja...@gmail.com>.
is the value of timeOut really small? i.e. you're not waiting long
enough for messages to be sent along the wire?

On 3/27/07, bgm_fr <bg...@hotmail.com> wrote:
>
> Hi all,
>
>   There's something weird happening with my application.
>
> My app consists in two queues : one for command and one for notification. So
> I got 2 producer/consumer couples.
> When everything (firstApp activeMq secondApp) is on the same computer,
> everything works fine. Troubles happen when we try to put the fisrt app and
> secondApp on two different computers. One way works fine (from firstApp to
> secondApp) but not the other way (secondApp to firstApp).
>
> What is really weird here is that when watching through jmx consol, we can
> see that the message from second to first is sent, that a consumer is
> listening on it (the one from firstApp), even that there was a dispatch to
> this consumer but still the consumer.receive(timeOut) returns null and the
> queue is not decreased.
>
> Another detail, if we put firstApp and secondApp on the same computer and
> activeMQ on another computer it works fine.
>
> I am becoming a bit crazy with this, has anyone got an idea ?
>
> Thanks in advance,
>
> --
> View this message in context: http://www.nabble.com/Queue-message-reception-failure-tf3475041s2354.html#a9699184
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Re: Queue message reception failure

Posted by bgm_fr <bg...@hotmail.com>.
Hi, 
  Thanks for your help. We found the problem. In fact the timeToLive
parameter was set to 1000 and then to 10000 but nothing changed, so we
decided not to set it up and everything works fine now. So we do believe
that it comes from the validity of messages we sent.

   The weird thing is that with the not working parameters (timeToLive set
to 1000 or 10000) but in asynchronous consumption (setMessageListener
instead of consumer.receive) it worked... Well it is ok for us now.

So thanks a lot for your help, 

Bye


Adrian Co wrote:
> 
> Weird. Can you post your activemq.xml and client code (at least the 
> connection factory creation, publish code snippet and listener snippet)...
> 
> bgm_fr wrote:
>> Hi all,
>>
>>   There's something weird happening with my application. 
>>
>> My app consists in two queues : one for command and one for notification.
>> So
>> I got 2 producer/consumer couples.
>> When everything (firstApp activeMq secondApp) is on the same computer,
>> everything works fine. Troubles happen when we try to put the fisrt app
>> and
>> secondApp on two different computers. One way works fine (from firstApp
>> to
>> secondApp) but not the other way (secondApp to firstApp).
>>
>> What is really weird here is that when watching through jmx consol, we
>> can
>> see that the message from second to first is sent, that a consumer is
>> listening on it (the one from firstApp), even that there was a dispatch
>> to
>> this consumer but still the consumer.receive(timeOut) returns null and
>> the
>> queue is not decreased.
>>   
>> Another detail, if we put firstApp and secondApp on the same computer and
>> activeMQ on another computer it works fine. 
>>
>> I am becoming a bit crazy with this, has anyone got an idea ?
>>
>> Thanks in advance,
>>
>>   
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Queue-message-reception-failure-tf3475041s2354.html#a9712022
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: Queue message reception failure

Posted by Adrian Co <ac...@exist.com>.
Weird. Can you post your activemq.xml and client code (at least the 
connection factory creation, publish code snippet and listener snippet)...

bgm_fr wrote:
> Hi all,
>
>   There's something weird happening with my application. 
>
> My app consists in two queues : one for command and one for notification. So
> I got 2 producer/consumer couples.
> When everything (firstApp activeMq secondApp) is on the same computer,
> everything works fine. Troubles happen when we try to put the fisrt app and
> secondApp on two different computers. One way works fine (from firstApp to
> secondApp) but not the other way (secondApp to firstApp).
>
> What is really weird here is that when watching through jmx consol, we can
> see that the message from second to first is sent, that a consumer is
> listening on it (the one from firstApp), even that there was a dispatch to
> this consumer but still the consumer.receive(timeOut) returns null and the
> queue is not decreased.
>   
> Another detail, if we put firstApp and secondApp on the same computer and
> activeMQ on another computer it works fine. 
>
> I am becoming a bit crazy with this, has anyone got an idea ?
>
> Thanks in advance,
>
>