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

[JWS] Container contains an empty log file

XMLWordPrintable

    • 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

      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

              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

                Created:
                Updated:
                Resolved: