E
eunever32
Hi
In 4.1.24 we were able to direct the output of RequestDumperValve to
its own log file
as follows:
<Engine name="Standalone" defaultHost="localhost" debug="0">
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt" timestamp="true"/>
With Tomcat 5.5 I can enable RequestDumperValve as follows:
<Engine name="Catalina" default="localhost">
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
to go to catalina.out
Is it possible to configure tomcat 5.5 such that the
RequestDumperValve goes to its own files (like with the Logger element
above) and the existing webapp logging statements continue to go to
catalina.out ?
I have tried using log4j.properties but can only configure such that
catalina.out is rotated.
The problem is that regular cat.debug statements get lost in the flood
of RequestDumperValve output
Thanks in advance
In 4.1.24 we were able to direct the output of RequestDumperValve to
its own log file
as follows:
<Engine name="Standalone" defaultHost="localhost" debug="0">
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt" timestamp="true"/>
With Tomcat 5.5 I can enable RequestDumperValve as follows:
<Engine name="Catalina" default="localhost">
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
to go to catalina.out
Is it possible to configure tomcat 5.5 such that the
RequestDumperValve goes to its own files (like with the Logger element
above) and the existing webapp logging statements continue to go to
catalina.out ?
I have tried using log4j.properties but can only configure such that
catalina.out is rotated.
The problem is that regular cat.debug statements get lost in the flood
of RequestDumperValve output
Thanks in advance