What are you trying to achieve even? Lifetime of a "normal business txn message" is in nano-seconds. You want to add these layers of auditing (supposedly) which will add significant overhead as there is no parallel inbuilt auditing capabilities. Which means amq will try to process your business txn and at the same time perform all the auditing (assuming this is even possible, which i dont think it is) and then move on to the next message. The "states" you are referring to "for threads" is used only for debugging. In a real live environment neither it is turned on by default nor used. Hence the question. What are you trying to achieve and what purpose such information serves?
-- View this message in context: http://activemq.2283324.n4.nabble.com/how-to-find-different-message-states-ideal-running-stop-in-active-MQ-tp4697649p4697698.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
