Right...that is what I am doing...the problem is that Tomcat's session
parameter is set to expire at 60 minutes but the continuation here is
expiring in far less 35 or so minutes.
I am catching it and telling them the "session" has expired and hence
they filed the bug as they were aware it should take 60 minutes, but it
was not.
I am using Cocoon 2.1.11, with Tomcat 7. Strangely it is fine with
Tomcat 6 but only has this problem with Tomcat 7.
Also, I am sure this has something to do with it--this page (which is
the only page on which this happens) has a "file upload widget" on it.
brgds
Paul
On 1/15/2012 2:43 PM, Robby Pelssers wrote:
Are you using cocoon2.1 or 2.2? From the stacktrace I can make out you're
using flowscript and you're using continuations as well. The problem is that
these continuations time out after some time which will result in the
stacktrace you see below. What you could do is catch this continuation
exception and handle it by forwarding the user to some page describing his
session expired.
Kind regards,
Robby
-----Original Message-----
From: Paul Joseph [mailto:[email protected]]
Sent: Friday, January 13, 2012 7:40 PM
To: [email protected]
Subject: connection reset?
Hi there,
On one (and seemingly only one) of my Cocoon application pages...if the
user leaves it untouched for some number of minutes that is LESS than
the session time out, when they come back and click to go to some other
page, they find it has errored out.
The cocoon.log is below....my questions are: why would it say
"connection reset by peer"? Is that why the subsequent message says
that the continuation is invalid?
thx.
Paul
==============
WARN (2012-01-13) 12:45.48:359 [access]
(/array/webtask/login/images/bsolution_o.gif)
"http-bio-9090"-exec-3/CocoonServlet: ClientAbortException:
java.net.SocketException: Connection reset by peer: socket write error
WARN (2012-01-13) 12:46.19:890 [access]
(/array/webtask/login/images/btimelog_o.gif)
"http-bio-9090"-exec-3/CocoonServlet: ClientAbortException:
java.net.SocketException: Connection reset by peer: socket write error
ERROR (2012-01-13) 13:26.05:265 [sitemap.handled-errors]
(/array/webtask/login/36251b2a35661f7a5c841889202f4a02531d1931.continue)
"http-bio-9090"-exec-4/ErrorHandlerHelper: The continuation ID
36251b2a35661f7a5c841889202f4a02531d1931 is invalid.
at<map:call> -
file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/array/webtask/login/sitemap.xmap:212:33
at<map:mount> -
file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/array/webtask/sitemap.xmap:74:62
org.apache.cocoon.components.flow.InvalidContinuationException: The
continuation ID 36251b2a35661f7a5c841889202f4a02531d1931 is invalid.
at<map:call> -
file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/array/webtask/login/sitemap.xmap:212:33
at<map:mount> -
file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/array/webtask/sitemap.xmap:74:62
at
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:792)
at
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:124)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
.....
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
