Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-101

logging-profile works for a servlet, but doesn't for a JSP

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.0.0.Alpha9
    • None
    • Logging
    • None
    • Hide
      1. Set the logging-profile in the description to a standalone instance.
      2. Deploy attached web app, logone/target/logone.war.
      3. Access a servlet, curl http://localhost:8080/logone/HogeServlet. Its log message appears in standalone/log/logone.log, as expected.
      4. Access a JSP, curl http://localhost:8080/logone/index.jsp. Its log message appears in standalone/log/server.log and CONSOLE, unexpectedly.
      Show
      Set the logging-profile in the description to a standalone instance. Deploy attached web app, logone/target/logone.war. Access a servlet, curl http://localhost:8080/logone/HogeServlet . Its log message appears in standalone/log/logone.log, as expected. Access a JSP, curl http://localhost:8080/logone/index.jsp . Its log message appears in standalone/log/server.log and CONSOLE, unexpectedly.

    Description

      Suppose the following logging-profile has been set in logging subsystem, and a web app has a proper entry in its MANIFEST.MF (Logging-Profile: logone). Then all messages via "com.example.logone" logger should go into a file, logone.log. It does so with a logger got in a servlet, but it doesn't work a logger got in a JSP.

                  <logging-profiles>
                <logging-profile name="logone">
                    <file-handler name="logone">
                        <level name="INFO"/>
                        <file relative-to="jboss.server.log.dir" path="logone.log"/>
                    </file-handler>
                    <logger category="com.example.logone">
                        <level name="INFO"/>
                    </logger>
                    <root-logger>
                        <level name="INFO"/>
                        <handlers>
                            <handler name="logone"/>
                        </handlers>
                    </root-logger>
                </logging-profile>
            </logging-profiles>

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WFLY-3857 Add JSP logging profile test

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-1814 Static loggers in modules could be created on wrong log context if logging profiles are used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-100 Upgrade JBoss Log Manager from 1.5.2.Final to 2.0.0.Beta1

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          relates to

          Feature Request - Feature requests from customers and/or users LOGMGR-111 ClassLoaderLogContextSelector should optionally include parent CL for context scanning

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              jperkins-rhn James Perkins
              rhn-support-onagano Osamu Nagano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: