Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-1841

[JWS] Container contains an empty log file

    XMLWordPrintable

Details

    • 1
    • Release Notes
    • Hide
      Cause: Openshift custom StdoutAccessLogValve and configuration created empty access.log file from parent class
      Consequence: Empty access.log file was created in the "jboss" user home inside the container
      Fix: Use standard org.apache.catalina.valves.AccessLogValve with configuration to redirect to stdout
      Result: No empty access.log file is now created inside the container
      Show
      Cause: Openshift custom StdoutAccessLogValve and configuration created empty access.log file from parent class Consequence: Empty access.log file was created in the "jboss" user home inside the container Fix: Use standard org.apache.catalina.valves.AccessLogValve with configuration to redirect to stdout Result: No empty access.log file is now created inside the container
    • CLOUD Maintenance Sprint 9

    Description

      When the server is started a new (empty) file is created - $HOME/logs/access_log.2017-06-26

      It is probably related to Tomcat Valve configuration

      Attachments

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-1784 [COMMON] Make the accessLog valve configurable

          • 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.
          • Verified
          relates to

          Feature Request - Feature requests from customers and/or users CLOUD-1820 StdoutAccessLogValve should also log X-Forwarded-For header

          • 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.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2811 [JDV] Container contains an empty log file

          • 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.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2152 [tracker] Sprint 12 release

          • 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

          Activity

            People

              wdecoste1@redhat.com William Decoste (Inactive)
              jpechane Jiri Pechanec
              Libor Fuka Libor Fuka
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: