On 06/08/2018 21:05, Chrifister wrote:
I'm still confused as to why the exceptions never made
it to catalina.out?
It depends where the problem occurs. If it occurs in application code
(e.g. inside a servlet of filter) then Tomcat will try and log it in
most specific log file (host or
I may have found the problem and solution. We went back and had a look at
all the logs, not just catalina.out. There was a localhost log made by
Tomcat and in there was a number of exceptions from when the application
was in that weird state. The exceptions were as follows:
java.io.IOException:
On 06/08/2018 16:54, Chrifister wrote:
Any help would be greatly appreciated.
No real ideas. Just requests for more information and an observation.
The 500 responses should have triggered stack traces in the logs. Can
you provide some sample stack traces of the errors you are seeing.
Hello Chris,
Definitely you have to increase the logging level. If your tomcat instance
is using JULI and you suspect from struts perhaps you could try to increase
the debugging level of struts in your
$CATALINA_BASE/conf/logging.properties:
org.apache.struts.level=FINE or FINEST
Hope it helps,
Hi,
Not an answer but just letting you my thinking on where I would look for
additional error messages that might help tell more of the story.
1) Any additional information in the individual Java Plugin Logs that tell more
of the story?
2) Can you increase the logging on the Tomcat side to try
