-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
To whom it may concern,
On 8/23/13 4:08 PM, Tomcat Random wrote:
I've deleted any reference in logging.properties to the console.
However the file rm'd catalina.out file still coming back on
restarts. Any ideas? catalina,out is now also
It's a service on RHEL: eg service tomcat start - that does call
catalina.sh so I can see where the catalina.out file is being generated.
I'll probably just comment that out, although without any console logging
in logging.properties it becomes quite light and captures System.err.print
messages
I've deleted any reference in logging.properties to the console. However
the file rm'd catalina.out file still coming back on restarts. Any ideas?
catalina,out is now also reporting java.util.logging.ErrorManager: 4:
Unable to create [logs]
Below is my altered logging.properties file:
My development setup is Win7 while my production is RHEL6. Both of the
environments have the same settings in conf/logging.properties but the
files in logs/ are slightly different.
The access logs are named the same way. but on RHEL there's no
tomcat7-stdout or tomcat7-stderr log files. Just
On 22/08/2013 16:44, Tomcat Random wrote:
My development setup is Win7 while my production is RHEL6. Both of the
environments have the same settings in conf/logging.properties but the
files in logs/ are slightly different.
The access logs are named the same way. but on RHEL there's no
2013/8/22 Tomcat Random tomcat.ran...@gmail.com:
My development setup is Win7 while my production is RHEL6. Both of the
environments have the same settings in conf/logging.properties but the
files in logs/ are slightly different.
The access logs are named the same way. but on RHEL there's no
