Apr 21st, 2011, 10:24 AM
JMS activites considered as frustrated by insight
I have an application deployed in TC server which contains a dozen of Message listeners connecting on an external JMS broker.
I kept the default config which means that the DMLC tries to get a message with a timeout of one second.
If I look to the status on the dashboard, my application is red and for every attempt to lookup a message, insight consider that the transaction last too long (1 sec vs the default 800 msec).
I am ok for the 800 msec for normal transactions (typically Spring MVC endpoints). Is this issue known?