We've been developing a XML/XSL/JSP/Servet based web application, running development on Tomcat 4.1.29, and connecting to an oracle 8i database using the oracle classes12.jar jdbc stuff.
The problem we are seeming to get, with alarming inconsistency, is that once a page errors (e.g. maybe a piece of sql failed in a jsp), tomcat returns a 503 error for the page. After this point, all subsequent attempts to access that page, result in
503 - This JSP has been marked unavailable.
the only way to get round this is to stop and restart tomcat.
All the code is in try/catch blocks, catching Exception, and not throwing them back any further up the chain, and at the end of all jsp's, database connections are terminated (again, in try catch blocks).
This is a major stability issue for us, as we cannot afford to deploy an application to the market that requires the entire webserver program to be stopped and restarted every time there's a minor problem.
I have searched everywhere i can think, and can't find anything to indicate if it's A) some web container configuration issue. B) some piece of programming the JSP's/Servlets that we are doing wrong.
(Also, even though the session timeout is disabled, variables in the session object seem to be vanishing after 10 minutes or so of user inactivity. does this one sound familiar to anyone?)
Senior Analyst Programmer.