tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: JSP suddenly causing problems [fixed -- still have questions]
Date Thu, 18 Jan 2007 21:42:41 GMT
Hash: SHA1


It turns out that my problem had to do with my altered deployment: a
properties file was not being copied into the right place, and my JSP's
init() method required that properties file to exist.

My servlet's init method, in this case, would have been throwing an
UnavailableException -- I catch all Exceptions in init and re-throw them
wrapped in an UnavailableException.

I would have expected to get my code's exception stack trace
/somewhere/, but didn't.

Looking at the source at

I can see that UnavailableException thrown from
JspServletWrapper.getServlet(), which is calling
theServlet.init(config), will jump out of getServlet back into
JspServletWrapper.service, which catches UnavailableException and
attempts (apparently, in this case) to return a "service unavailable"
HTTP status code.

For some reason, the response has already been committed (strange, as no
output whatsoever has been generated) and I end up getting this
exception. The result is that my exception and the stack trace are

Any ideas as to how my response could have been committed before
generating any output? I realize that my problem has been resolved and I
should probably be thankful for that, but I'm interested in what could
have caused this odd set of circumstances.

- -chris

Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla -


To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message