https://bz.apache.org/bugzilla/show_bug.cgi?id=69395
--- Comment #8 from Agostino Sarubbo <agostino.saru...@gmail.com> --- Hello Mark, sorry for the late reply. I'm not the developer of that application and in general I'm not a developer so I can speak with a limited knowledge. We had so far two distinct problems: The first was related to an "Empty JDBC URI when using a jdbc connection pool" and was resolved by adding '<load-on-startup>1</load-on-startup>' in web.xml The other problem we are facing with >9.0.93 is that we are getting error 500 on simple jsp and tomcat does not show any stacktrace for that. So at the begin, there was a confusion because we hit those two problems without understand that they were two distinct problems. I tried to activate all possible logs but tomcat still does not print anything on error 500. Could you suggest what to modify to get a meaningful stacktrace ? NOTE: since we are deploying a year-old untouched war we think that this error 500 comes from a tomcat change in >9.0.93 Thanks in advance -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
