thanks Pat, that caught the exception.

does anyone know what will be the alternative to making a call to
RequestContext to get the Session? I thought it might be
getInfrastructure.getRequest().getSession(boolean) ?





On 12/22/05, Patrick Casey < [EMAIL PROTECTED]> wrote:
>
>
>         I saw that error a lot in my existing 3.0 application. In my case
> I
> eventually tracked it down to a low level socket write error (my server
> was
> reporting that the browser shut the socket before it finished sending the
> full stream). I'm sure there's another underlying cause e.g. the browser
> didn't do that on a whim, but I couldn't figure out how to fix it.
>
>         I ended up having to superclass BaseEngine and turn the error
> message into a noop just to keep my log from filling up with that
> particular
> error message.
>
>         If you want to get rid of it, superclass BaseEngine, and override
> reportError like this.
>
> public void reportException(String reportTitle, Throwable ex) {
>                 String name = ex.getClass().getCanonicalName();
>                 if (name.endsWith("ClientAbortException")) {
>                         Log.debug("Threw one of those annoying IE only
> flush
> errors");
>                         return;
>                 }
>                 super.reportException(reportTitle,ex);
>         }
>
>         --- Pat
>
> > -----Original Message-----
> > From: Ray O'Meara [mailto: [EMAIL PROTECTED]
> > Sent: Thursday, December 22, 2005 9:31 AM
> > To: [email protected]
> > Subject: Tapoestry 3 -> Tapestry 4 upgrade question
> >
> > Im using a combination of Tapestry,Spring,Acegi and Hibernate in a
> project
> > and since ive upgraded to Tapestry 4.0 a failure occurs in an external
> > link
> > to a page which allows me to log out of the app and activate the Login
> > page.
> >
> >
> > A call to the RequestContext to get the Session invalidated results in:
> >
> > WARN http-8080-Processor25 tapestry.error.RequestExceptionReporter -
> > Exception during post-request cleanup: setAttribute: Session already
> > invalidated
> > java.lang.IllegalStateException: setAttribute: Session already
> invalidated
> >
> > Is there a solution to this, or have I missed out on something while I
> did
> > the upgrade?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to