thanks for your reply with the solution. Just fyi: the timeStampPlugin can
help in this situation: see http://activemq.apache.org/timestampplugin.html
2009/12/18 couzteau
>
> Turns out the problems was having explicitQosEnabled=true and a short
> timeToLive. The system clocks of producer, broker
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
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.
On your live server ,run jconsole.exe (comes with JDK)and connect to the
java process pertaining to your application.
You can see the threads used by active mq , the port numbers for the JMS
receiver/sender in your application.
Also turn on the debug mode of active mq ,
http://activemq.apache.org
