Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-3009

Change of java Thread name is not reflecting in log4j2 logs (pattern %t)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.8.2
    • None
    • Core, Pattern Converters
    • None

    Description

      I have Java based application with a single thread connected to JBOSS MQ. Whenever there is a message in the queue then it pulls the message and sets the thread name with one of the message's attribute (REQUEST_ID) and continues processing. After application startup, the logging is fine for the first message. But from the second message, the change in the thread name is not reflecting in the logs.

      Example code

      private static Logger logger = LogManager.getLogger(EngineManager.class.getName());
      
      private synchronized void onMessage(javax.jms.Message msg) {
          Thread.currentThread().setName(msg.getStringProperty("REQUEST_ID"));
          logger.info("Received a Message Event: Time spent:" + (System.currentTimeMillis()-msg.getJMSTimestamp()) + "ms");
          // ...
      }
      

      Configuration

      appender.console.layout.pattern = %d\{ABSOLUTE} %c{1} [%t] - %m%n
      

      Output

      19:29:52,726 EngineManager [sddsdsdgdd-dfvdddbfvs-2343412] - Received a Message Event: Time spent: 44ms
      

       

      Rest everything is fine that's why I have given small portion of the code. What I need is when there is a second message (so on) in the queue then above REQUEST_ID should change in the logs. It is always same for all the messages. I tried different ways like LoggerContext.reconfigure()LogManager.shutdown() and then getLogger() etc but couldn't succeed.

      This used to work fine with log4j 1x where the change in the thread name immediately reflects in the logs.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rohan438 Rohan Ramchander
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 336h
                336h
                Remaining:
                Remaining Estimate - 336h
                336h
                Logged:
                Time Spent - Not Specified
                Not Specified