Turns out the problems was having explicitQosEnabled=true and a short
timeToLive. The system clocks of producer, broker and consumer deviated
hence messages were expired before they were ever delivered.
--
View this message in context:
http://old.nabble.com/Debug-JMS-environment-tp18426484p26851
Thanks for the info!
I integrated 5.3-snapshot but ran into compile issues with the latest jar -
So I abandoned that.
Gary Tully wrote:
>
> in the absence of a test case, the best approach is to try out a
> 5.3-SNAPSHOT
>
> 2009/7/30 couzteau
>
>>
>> Has th
Has this been solved yet? I'm seeing it with 5.2.0.
I'm seeing an issue that occurs on some machines (where machines are
identical regarding OS, Java version and hardware).
Consumers that are on the same machine as the producer usually work fine.
It's a major blocker for us - any comments high
Hi,
My JMS system does not work reliably. Some machines receive messages and
others do not. My setup is simple:
- The production servers (running JBoss 4.2.2GA, JDK 1.6.0_10 on Red Hat
Enterprise Linux ES release 4 , ActiveMQ 5.1 together with Spring 2.5) is
hosting a web service that also act
Thank you.
That was just what I was looking for.
jacques
--
View this message in context:
http://www.nabble.com/Debug-JMS-environment-tp18426484p18452317.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I have added JMS support a web app and ran into an expected problem when I
went live with the app. All test machines worked great but the live server
has a different and complex network environment that I don't have control
of. So the problem is that messages are not being received by clients.
