yes these are custom logs that I can control. so seems like MDC can solve my
problem. will start looking into it. thanks for the suggestion/solution!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I am trying to trace the lifetime of a message in the client application log.
That is in my application's onMessage(Message p_message) method I have
different log statements which
get printed under the thread ID: "ActiveMQ Session Task".
Like below:
[INFO ] 2018-11-27 16:29:57,642 [ActiveMQ
I am running ActiveMQ 5.15.5 as a standalone broker and my spring application
is connecting to it.
I wanted to know if I can log the Task-ID that the broker logs, in the
client application logs.
Currently application logs look like:
INFO ] 2018-11-29 09:52:19,144 [ActiveMQ Session Task]