You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by snekam <ka...@bah.com> on 2018/12/03 17:19:23 UTC

Re: Logging Task Ids from ActiveMQ broker to the producer application

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 Session Task] HydrationServiceImpl
- ===>  START: dehydrate
[INFO ] 2018-11-27 16:29:57,642 [ActiveMQ Session Task] HydrationDaoImpl -
==> START: countCor
[INFO ] 2018-11-27 16:29:57,649 [ActiveMQ Session Task] HydrationDaoImpl -
==> END: countCor
[INFO ] 2018-11-27 16:29:57,649 [ActiveMQ Session Task] HydrationDaoImpl -
==> START: purge for id = 82559
[INFO ] 2018-11-27 16:29:57,664 [ActiveMQ Session Task] HydrationDaoImpl -
==> END: purge
[INFO ] 2018-11-27 16:29:57,664 [ActiveMQ Session Task] HydrationServiceImpl
- ==> END: dehydrate


So if more than 1 message is being worked on then all get the same thread
ID:- [ActiveMQ Session Task] 

Thus there is no way for me to categorize the logs for different messages.

Is there a way to be able to tell, for which message consume is the log
statement for?




--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Logging Task Ids from ActiveMQ broker to the producer application

Posted by snekam <ka...@bah.com>.
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

Re: Logging Task Ids from ActiveMQ broker to the producer application

Posted by Tim Bain <tb...@alumni.duke.edu>.
So these are all custom log messages over which you have control? Can you
simply add the JMSMessageID to each one? Or put it into the MDC (
https://logging.apache.org/log4j/2.x/manual/thread-context.html, or
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html if
you're using Log4J 1.x)?

Tim

On Mon, Dec 3, 2018, 10:19 AM snekam <kamathaldonker_sneha@bah.com wrote:

> 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 Session Task]
> HydrationServiceImpl
> - ===>  START: dehydrate
> [INFO ] 2018-11-27 16:29:57,642 [ActiveMQ Session Task] HydrationDaoImpl -
> ==> START: countCor
> [INFO ] 2018-11-27 16:29:57,649 [ActiveMQ Session Task] HydrationDaoImpl -
> ==> END: countCor
> [INFO ] 2018-11-27 16:29:57,649 [ActiveMQ Session Task] HydrationDaoImpl -
> ==> START: purge for id = 82559
> [INFO ] 2018-11-27 16:29:57,664 [ActiveMQ Session Task] HydrationDaoImpl -
> ==> END: purge
> [INFO ] 2018-11-27 16:29:57,664 [ActiveMQ Session Task]
> HydrationServiceImpl
> - ==> END: dehydrate
>
>
> So if more than 1 message is being worked on then all get the same thread
> ID:- [ActiveMQ Session Task]
>
> Thus there is no way for me to categorize the logs for different messages.
>
> Is there a way to be able to tell, for which message consume is the log
> statement for?
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>