Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5114

Line number logging lists incorrect line

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.1
    • EAP 5.0.1, EWP 5.0.1
    • Build
    • None
    • Hide

      Add a %L to the ConversionPattern of a layout in $JBOSS_HOME/sever/$PROFILE/conf/jboss-log4j.xml and check the line numbers output with the line numbers from the corresponding class. For EAP 5.0.1, the INFO message:

      2010-09-21 11:32:23,380 INFO [org.jboss.web.WebService] (main) Using RMI server codebase: http://127.0.0.1:8083/

      Should occur on line 309

      Show
      Add a %L to the ConversionPattern of a layout in $JBOSS_HOME/sever/$PROFILE/conf/jboss-log4j.xml and check the line numbers output with the line numbers from the corresponding class. For EAP 5.0.1, the INFO message: 2010-09-21 11:32:23,380 INFO [org.jboss.web.WebService] (main) Using RMI server codebase: http://127.0.0.1:8083/ Should occur on line 309
    • Release Notes
    • The logging system can be configured to log the Java source line number where the logging is invoked. Prior to this fix, the line number displayed could list the incorrect line number.
    • Not Yet Documented

      When the jboss-log4j.xml PatternLayout is configured to output line numbers (using '%L' in the ConversionPattern) the incorrect line number is output. So, for example, using a conversion pattern of "%d %-5p [%c:%L] (%t) %m%n" in the server.log you will see:

      2010-09-21 11:32:23,380 INFO [org.jboss.web.WebService:296] (main) Using RMI server codebase: http://127.0.0.1:8083/

      instead of the correct

      2010-09-21 11:32:23,380 INFO [org.jboss.web.WebService:309] (main) Using RMI server codebase: http://127.0.0.1:8083/

              rhn-support-miclark Mike Clark
              rhn-support-miclark Mike Clark
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: