Asking again: Tomcat silently stops working, very strange exceptions in catalina.out

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Asking again: Tomcat silently stops working, very strange exceptions in catalina.out

Leon Rosenberg-3
Hi,

noone has an idea or has experienced similar behaviour?

Recapitulation:
At some stage tomcat starts throwing exception which actually can't
happen, mostly telling  me that beans aren't found in session scope,
in jsps which could only be called after a bean has been put into the
session scope. It also throws SocketErrors, ClientAbortExceptions and
PipeBrokenException in attempt to deliver static error page (404.html
or 500.html).

Minutes later it just stops responding, with no futher errors in the
logs. The load on the machine drops to zero. After calling shutdown.sh
and startup.sh tomcat continues normally. Interesting, but at some
point of time multiple production servers are affected, as if a user
would cause this.

Any ideas?

Leon

On 2/28/06, Leon Rosenberg <[hidden email]> wrote:

> On 2/28/06, Filip Hanik - Dev Lists <[hidden email]> wrote:
> >  >javax.servlet.jsp.JspException: No bean found under attribute key result
> >
> > this is a regular struts exception, it is expecting a bean in one of the
> > scopes (request,page,session), but it is not there.
>
> 'The funny thing is, that there is actually no way for the bean to
> "not be there"...
> the code from the appropriate action looks like this:
>
>                 if (!r.isValid()) {
>                         if(r.getErrorMessage() != null && r.getErrorMessage().startsWith("PLZ")) {
>                                 errors.add("search", new ActionError("errors.zip.notexisting"));
>                         } else {
>                                 throw new RuntimeException("Query failed:
> "+IResultStatus.STATUS_DESC[r.getStatus()]+"("+r.getErrorMessage()+")");
>                         }
>                 } else {
>
>                         ResultBean result = new ResultBean();
> ... omitted...
>                         addBeanToSession(req, ISessionConstantsNames.SEARCH_BEAN_RESULT, result);
>                         addBeanToSession(req,
> ISessionConstantsNames.SEARCH_BEAN_LAST_QUERY, r.getSourceQuery());
>                 }
>
>                 if(errors.size() > 0) {
>                         saveErrors(req, errors);
>                         proceedErrorHandling(req);
>                         return mapping.getInputForward();
>                 }
>
>                 return mapping.findForward(view); <-- only this return leads to the
> jsp in the logs.
>
> if the jsp-in-question mapping is returned, the ResultBean must be in
> session, or the session is corrupted.
>
> >
> > your second error seems to be a result of a client disconnecting
> >
> > http://tomcat.apache.org/tomcat-5.0-doc/catalina/docs/api/org/apache/catalina/connector/ClientAbortException.html
>
> Sure, but that doesn't explain why tomcat stops responding, does it?
>
> >
> > Filip
>
> Leon
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]