You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Paul Joseph <pj...@gmail.com> on 2009/11/18 12:32:58 UTC
ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Hi There,
On one particular request, I get a ClientAbort exception, connection
reset error (see below.) Any reason why this could be?
I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
and Cocoon 2.1.11.
I have seen a similar thread, but with no resolution.
thx.
Paul
The error is as follows:
WARN (2009-11-17) 10:58.04:991 [access]
(/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
ClientAbortException: java.net.SocketException: Connection reset by
peer: socket write error
ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
http-9090-Processor23/NativeJavaMethod: java.lang.IllegalStateException:
getAttribute: Session already invalidated
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Paul Joseph <pj...@gmail.com>.
Based on looking at the system it seems to happen most when the disk
response times are slow or when a lot of information is being logged.
Paul
Paul Joseph wrote:
> Hi There,
>
> On one particular request, I get a ClientAbort exception, connection
> reset error (see below.) Any reason why this could be?
>
> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
> and Cocoon 2.1.11.
>
> I have seen a similar thread, but with no resolution.
>
> thx.
> Paul
>
> The error is as follows:
> WARN (2009-11-17) 10:58.04:991 [access]
> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
> ClientAbortException: java.net.SocketException: Connection reset by
> peer: socket write error
> ERROR (2009-11-17) 10:58.25:037 [flow]
> (/array/webtask/request/reqMine)
> http-9090-Processor23/NativeJavaMethod:
> java.lang.IllegalStateException: getAttribute: Session already
> invalidated
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection
reset by peer: socket write error
Posted by Debiprasanna Tripathy <de...@gmail.com>.
Hi Paul,
This usually happens when a client canceled the request, e.g. by clicking
'Cancel' while the page is still being loaded.
You can do the following code to avoid to log
catch(Exception e){ // catch the Exception
String clientAbortException = "";
index = e.toString().indexOf(":");
if(index != 0){
clientAbortException = e.toString().substring(0, index );
}
if("ClientAbortException" .equalsIgnoreCase(clientAbortException)) { //
check it the exception is the
// ClientAbortException then do nothing
// Down Loading Canceled by the Client
if (out != null) {
try{
if(out != null)
out.close(); // close the output stream
if(in != null)
in.close(); // close the input stream
}
catch(Exception ee){
// catch nothing
}
}
}
}
Regards,
Debiprasanna Tripathy
--
View this message in context: http://old.nabble.com/ClientAbortException%3A--java.net.SocketException%3A-Connection-reset-by-peer%3A-socket-write-error-tp26406293p26618446.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Paul Joseph <pj...@gmail.com>.
My bad Joerg, thanks for pointing it out...I wrongly assumed the first
caused the second.
Any ideas what is causing the second--which is what I was trying to solve...
thx.
Paul
Jörg Heinicke wrote:
> Is that really the correct stacktrace? It has a NPE and occured half an hour after the ClientAbortException.
>
> Joerg
>
> -------- Original-Nachricht --------
>
>> Datum: Wed, 18 Nov 2009 17:32:59 -0500
>> Von: Paul Joseph <pj...@gmail.com>
>> An: users@cocoon.apache.org
>> Betreff: Re: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
>>
>
>
>> Hi Joerg,
>>
>> Let me check with the customer re. any proxies or firewalls...
>>
>> The stack trace is as follows below.
>>
>> rgds
>> Paul
>> WARN (2009-11-17) 10:23.59:411 [access]
>> (/array/webtask/search/6e371b2c4e17167324502788487a6a670d3c176b.continue)
>> http-9090-Processor20/CocoonServlet: ClientAbortException:
>> java.net.SocketException: Connection reset by peer: socket write error
>> ERROR (2009-11-17) 10:57.54:945 [sitemap.handled-errors]
>> (/array/webtask/search/58720f390c627968884c05248252457a5c6c1b7b.continue)
>> http-9090-Processor23/ErrorHandlerHelper: Sitemap: error calling
>> continuation
>> at <map:call> -
>> file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/array/webtask/search/sitemap.xmap:41:33
>> at <map:mount> -
>> file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/array/webtask/sitemap.xmap:70:62
>> java.lang.NullPointerException
>> at
>> org.apache.cocoon.forms.flow.javascript.ScriptableWidget.get(ScriptableWidget.java:111)
>> at
>> org.mozilla.javascript.ScriptRuntime.getProp(ScriptRuntime.java:723)
>> at
>> org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:694)
>> at
>> org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190)
>> at
>> org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138)
>> at
>> org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121)
>> at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
>> at
>> org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1591)
>> at
>> org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:841)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:124)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
>> at
>> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
>> at
>> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
>> at
>> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:118)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
>> at
>> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
>> at
>> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
>> at
>> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:118)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
>> at
>> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
>> at
>> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
>> at
>> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
>> at
>> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
>> at
>> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
>> at org.apache.cocoon.Cocoon.process(Cocoon.java:699)
>> at
>> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1154)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
>> at
>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>> at
>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>> at
>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>> at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
>> at java.lang.Thread.run(Unknown Source)
>>
>>
>>
>> Jörg Heinicke wrote:
>>
>>> Hi Paul,
>>>
>>> no, it usually has nothing to do with the session. I see that you have
>>>
>> flow involved though. I'm not sure about the internal request related to
>> that setup. How do the stack traces for both exceptions look like?
>>
>>> What times for request processing are we talking about in case the
>>>
>> socket connection is dropped?
>>
>>> A socket timeout can be caused by network components like firewalls or
>>>
>> proxies. I'm not aware of such settings in Cocoon or Tomcat (and never had
>> problems with long-running requests).
>>
>>> Regards,
>>> Joerg
>>>
>>> -------- Original-Nachricht --------
>>>
>>>
>>>> Datum: Wed, 18 Nov 2009 15:37:31 -0500
>>>> Von: Paul Joseph <pj...@gmail.com>
>>>> An: users@cocoon.apache.org
>>>> Betreff: Re: ClientAbortException: java.net.SocketException:
>>>>
>> Connection reset by peer: socket write error
>>
>>>>
>>>>
>>>
>>>
>>>> Hi Jörg,
>>>>
>>>> Ok...thanks I'll ask the users about that...
>>>>
>>>> But does that invalidate the session? This ClientAbortException is
>>>> always followed by this:
>>>>
>>>> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
>>>> http-9090-Processor23/NativeJavaMethod:
>>>>
>> java.lang.IllegalStateException:
>>
>>>> getAttribute: Session already invalidated
>>>>
>>>> rgds
>>>> Paul
>>>>
>>>> Jörg Heinicke wrote:
>>>>
>>>>
>>>>> Hi Paul,
>>>>>
>>>>> this usually happens if the client canceled the request, e.g. by
>>>>>
>>>>>
>>>> clicking 'Stop' while the page is still being loaded.
>>>>
>>>>
>>>>> Regards,
>>>>> Joerg
>>>>>
>>>>> -------- Original-Nachricht --------
>>>>>
>>>>>
>>>>>
>>>>>> Datum: Wed, 18 Nov 2009 06:32:58 -0500
>>>>>> Von: Paul Joseph <pj...@gmail.com>
>>>>>> An: users@cocoon.apache.org
>>>>>> Betreff: ClientAbortException: java.net.SocketException: Connection
>>>>>>
>>>>>>
>>>> reset by peer: socket write error
>>>>
>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Hi There,
>>>>>>
>>>>>> On one particular request, I get a ClientAbort exception, connection
>>>>>> reset error (see below.) Any reason why this could be?
>>>>>>
>>>>>> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
>>>>>> and Cocoon 2.1.11.
>>>>>>
>>>>>> I have seen a similar thread, but with no resolution.
>>>>>>
>>>>>> thx.
>>>>>> Paul
>>>>>>
>>>>>> The error is as follows:
>>>>>> WARN (2009-11-17) 10:58.04:991 [access]
>>>>>> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
>>>>>> ClientAbortException: java.net.SocketException: Connection reset by
>>>>>> peer: socket write error
>>>>>> ERROR (2009-11-17) 10:58.25:037 [flow]
>>>>>>
>> (/array/webtask/request/reqMine)
>>
>>>>>> http-9090-Processor23/NativeJavaMethod:
>>>>>>
>>>>>>
>>>> java.lang.IllegalStateException:
>>>>
>>>>
>>>>>> getAttribute: Session already invalidated
>>>>>>
>>>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Jörg Heinicke <Jo...@gmx.de>.
Is that really the correct stacktrace? It has a NPE and occured half an hour after the ClientAbortException.
Joerg
-------- Original-Nachricht --------
> Datum: Wed, 18 Nov 2009 17:32:59 -0500
> Von: Paul Joseph <pj...@gmail.com>
> An: users@cocoon.apache.org
> Betreff: Re: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
> Hi Joerg,
>
> Let me check with the customer re. any proxies or firewalls...
>
> The stack trace is as follows below.
>
> rgds
> Paul
> WARN (2009-11-17) 10:23.59:411 [access]
> (/array/webtask/search/6e371b2c4e17167324502788487a6a670d3c176b.continue)
> http-9090-Processor20/CocoonServlet: ClientAbortException:
> java.net.SocketException: Connection reset by peer: socket write error
> ERROR (2009-11-17) 10:57.54:945 [sitemap.handled-errors]
> (/array/webtask/search/58720f390c627968884c05248252457a5c6c1b7b.continue)
> http-9090-Processor23/ErrorHandlerHelper: Sitemap: error calling
> continuation
> at <map:call> -
> file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/array/webtask/search/sitemap.xmap:41:33
> at <map:mount> -
> file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/array/webtask/sitemap.xmap:70:62
> java.lang.NullPointerException
> at
> org.apache.cocoon.forms.flow.javascript.ScriptableWidget.get(ScriptableWidget.java:111)
> at
> org.mozilla.javascript.ScriptRuntime.getProp(ScriptRuntime.java:723)
> at
> org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:694)
> at
> org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190)
> at
> org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138)
> at
> org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121)
> at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
> at
> org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1591)
> at
> org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:841)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:124)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
> at
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
> at
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
> at
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:118)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
> at
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
> at
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
> at
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:118)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
> at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
> at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
> at
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
> at
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
> at
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
> at org.apache.cocoon.Cocoon.process(Cocoon.java:699)
> at
> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1154)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
> at java.lang.Thread.run(Unknown Source)
>
>
>
> Jörg Heinicke wrote:
> > Hi Paul,
> >
> > no, it usually has nothing to do with the session. I see that you have
> flow involved though. I'm not sure about the internal request related to
> that setup. How do the stack traces for both exceptions look like?
> >
> > What times for request processing are we talking about in case the
> socket connection is dropped?
> >
> > A socket timeout can be caused by network components like firewalls or
> proxies. I'm not aware of such settings in Cocoon or Tomcat (and never had
> problems with long-running requests).
> >
> > Regards,
> > Joerg
> >
> > -------- Original-Nachricht --------
> >
> >> Datum: Wed, 18 Nov 2009 15:37:31 -0500
> >> Von: Paul Joseph <pj...@gmail.com>
> >> An: users@cocoon.apache.org
> >> Betreff: Re: ClientAbortException: java.net.SocketException:
> Connection reset by peer: socket write error
> >>
> >
> >
> >> Hi Jörg,
> >>
> >> Ok...thanks I'll ask the users about that...
> >>
> >> But does that invalidate the session? This ClientAbortException is
> >> always followed by this:
> >>
> >> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
> >> http-9090-Processor23/NativeJavaMethod:
> java.lang.IllegalStateException:
> >> getAttribute: Session already invalidated
> >>
> >> rgds
> >> Paul
> >>
> >> Jörg Heinicke wrote:
> >>
> >>> Hi Paul,
> >>>
> >>> this usually happens if the client canceled the request, e.g. by
> >>>
> >> clicking 'Stop' while the page is still being loaded.
> >>
> >>> Regards,
> >>> Joerg
> >>>
> >>> -------- Original-Nachricht --------
> >>>
> >>>
> >>>> Datum: Wed, 18 Nov 2009 06:32:58 -0500
> >>>> Von: Paul Joseph <pj...@gmail.com>
> >>>> An: users@cocoon.apache.org
> >>>> Betreff: ClientAbortException: java.net.SocketException: Connection
> >>>>
> >> reset by peer: socket write error
> >>
> >>>>
> >>>>
> >>>
> >>>
> >>>> Hi There,
> >>>>
> >>>> On one particular request, I get a ClientAbort exception, connection
> >>>> reset error (see below.) Any reason why this could be?
> >>>>
> >>>> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
> >>>> and Cocoon 2.1.11.
> >>>>
> >>>> I have seen a similar thread, but with no resolution.
> >>>>
> >>>> thx.
> >>>> Paul
> >>>>
> >>>> The error is as follows:
> >>>> WARN (2009-11-17) 10:58.04:991 [access]
> >>>> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
> >>>> ClientAbortException: java.net.SocketException: Connection reset by
> >>>> peer: socket write error
> >>>> ERROR (2009-11-17) 10:58.25:037 [flow]
> (/array/webtask/request/reqMine)
> >>>> http-9090-Processor23/NativeJavaMethod:
> >>>>
> >> java.lang.IllegalStateException:
> >>
> >>>> getAttribute: Session already invalidated
> >>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Paul Joseph <pj...@gmail.com>.
Hi Joerg,
Let me check with the customer re. any proxies or firewalls...
The stack trace is as follows below.
rgds
Paul
WARN (2009-11-17) 10:23.59:411 [access]
(/array/webtask/search/6e371b2c4e17167324502788487a6a670d3c176b.continue)
http-9090-Processor20/CocoonServlet: ClientAbortException:
java.net.SocketException: Connection reset by peer: socket write error
ERROR (2009-11-17) 10:57.54:945 [sitemap.handled-errors]
(/array/webtask/search/58720f390c627968884c05248252457a5c6c1b7b.continue)
http-9090-Processor23/ErrorHandlerHelper: Sitemap: error calling
continuation
at <map:call> -
file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/array/webtask/search/sitemap.xmap:41:33
at <map:mount> -
file:///C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/array/webtask/sitemap.xmap:70:62
java.lang.NullPointerException
at
org.apache.cocoon.forms.flow.javascript.ScriptableWidget.get(ScriptableWidget.java:111)
at org.mozilla.javascript.ScriptRuntime.getProp(ScriptRuntime.java:723)
at
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:694)
at
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190)
at
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138)
at
org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121)
at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
at
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1591)
at
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:841)
at
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:124)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:118)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:118)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:254)
at org.apache.cocoon.Cocoon.process(Cocoon.java:699)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Unknown Source)
Jörg Heinicke wrote:
> Hi Paul,
>
> no, it usually has nothing to do with the session. I see that you have flow involved though. I'm not sure about the internal request related to that setup. How do the stack traces for both exceptions look like?
>
> What times for request processing are we talking about in case the socket connection is dropped?
>
> A socket timeout can be caused by network components like firewalls or proxies. I'm not aware of such settings in Cocoon or Tomcat (and never had problems with long-running requests).
>
> Regards,
> Joerg
>
> -------- Original-Nachricht --------
>
>> Datum: Wed, 18 Nov 2009 15:37:31 -0500
>> Von: Paul Joseph <pj...@gmail.com>
>> An: users@cocoon.apache.org
>> Betreff: Re: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
>>
>
>
>> Hi Jörg,
>>
>> Ok...thanks I'll ask the users about that...
>>
>> But does that invalidate the session? This ClientAbortException is
>> always followed by this:
>>
>> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
>> http-9090-Processor23/NativeJavaMethod: java.lang.IllegalStateException:
>> getAttribute: Session already invalidated
>>
>> rgds
>> Paul
>>
>> Jörg Heinicke wrote:
>>
>>> Hi Paul,
>>>
>>> this usually happens if the client canceled the request, e.g. by
>>>
>> clicking 'Stop' while the page is still being loaded.
>>
>>> Regards,
>>> Joerg
>>>
>>> -------- Original-Nachricht --------
>>>
>>>
>>>> Datum: Wed, 18 Nov 2009 06:32:58 -0500
>>>> Von: Paul Joseph <pj...@gmail.com>
>>>> An: users@cocoon.apache.org
>>>> Betreff: ClientAbortException: java.net.SocketException: Connection
>>>>
>> reset by peer: socket write error
>>
>>>>
>>>>
>>>
>>>
>>>> Hi There,
>>>>
>>>> On one particular request, I get a ClientAbort exception, connection
>>>> reset error (see below.) Any reason why this could be?
>>>>
>>>> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
>>>> and Cocoon 2.1.11.
>>>>
>>>> I have seen a similar thread, but with no resolution.
>>>>
>>>> thx.
>>>> Paul
>>>>
>>>> The error is as follows:
>>>> WARN (2009-11-17) 10:58.04:991 [access]
>>>> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
>>>> ClientAbortException: java.net.SocketException: Connection reset by
>>>> peer: socket write error
>>>> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
>>>> http-9090-Processor23/NativeJavaMethod:
>>>>
>> java.lang.IllegalStateException:
>>
>>>> getAttribute: Session already invalidated
>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Jörg Heinicke <Jo...@gmx.de>.
Hi Paul,
no, it usually has nothing to do with the session. I see that you have flow involved though. I'm not sure about the internal request related to that setup. How do the stack traces for both exceptions look like?
What times for request processing are we talking about in case the socket connection is dropped?
A socket timeout can be caused by network components like firewalls or proxies. I'm not aware of such settings in Cocoon or Tomcat (and never had problems with long-running requests).
Regards,
Joerg
-------- Original-Nachricht --------
> Datum: Wed, 18 Nov 2009 15:37:31 -0500
> Von: Paul Joseph <pj...@gmail.com>
> An: users@cocoon.apache.org
> Betreff: Re: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
> Hi Jörg,
>
> Ok...thanks I'll ask the users about that...
>
> But does that invalidate the session? This ClientAbortException is
> always followed by this:
>
> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
> http-9090-Processor23/NativeJavaMethod: java.lang.IllegalStateException:
> getAttribute: Session already invalidated
>
> rgds
> Paul
>
> Jörg Heinicke wrote:
> > Hi Paul,
> >
> > this usually happens if the client canceled the request, e.g. by
> clicking 'Stop' while the page is still being loaded.
> >
> > Regards,
> > Joerg
> >
> > -------- Original-Nachricht --------
> >
> >> Datum: Wed, 18 Nov 2009 06:32:58 -0500
> >> Von: Paul Joseph <pj...@gmail.com>
> >> An: users@cocoon.apache.org
> >> Betreff: ClientAbortException: java.net.SocketException: Connection
> reset by peer: socket write error
> >>
> >
> >
> >> Hi There,
> >>
> >> On one particular request, I get a ClientAbort exception, connection
> >> reset error (see below.) Any reason why this could be?
> >>
> >> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
> >> and Cocoon 2.1.11.
> >>
> >> I have seen a similar thread, but with no resolution.
> >>
> >> thx.
> >> Paul
> >>
> >> The error is as follows:
> >> WARN (2009-11-17) 10:58.04:991 [access]
> >> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
> >> ClientAbortException: java.net.SocketException: Connection reset by
> >> peer: socket write error
> >> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
> >> http-9090-Processor23/NativeJavaMethod:
> java.lang.IllegalStateException:
> >> getAttribute: Session already invalidated
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Paul Joseph <pj...@gmail.com>.
Hi Jörg,
Ok...thanks I'll ask the users about that...
But does that invalidate the session? This ClientAbortException is
always followed by this:
ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
http-9090-Processor23/NativeJavaMethod: java.lang.IllegalStateException:
getAttribute: Session already invalidated
rgds
Paul
Jörg Heinicke wrote:
> Hi Paul,
>
> this usually happens if the client canceled the request, e.g. by clicking 'Stop' while the page is still being loaded.
>
> Regards,
> Joerg
>
> -------- Original-Nachricht --------
>
>> Datum: Wed, 18 Nov 2009 06:32:58 -0500
>> Von: Paul Joseph <pj...@gmail.com>
>> An: users@cocoon.apache.org
>> Betreff: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
>>
>
>
>> Hi There,
>>
>> On one particular request, I get a ClientAbort exception, connection
>> reset error (see below.) Any reason why this could be?
>>
>> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
>> and Cocoon 2.1.11.
>>
>> I have seen a similar thread, but with no resolution.
>>
>> thx.
>> Paul
>>
>> The error is as follows:
>> WARN (2009-11-17) 10:58.04:991 [access]
>> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
>> ClientAbortException: java.net.SocketException: Connection reset by
>> peer: socket write error
>> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
>> http-9090-Processor23/NativeJavaMethod: java.lang.IllegalStateException:
>> getAttribute: Session already invalidated
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: ClientAbortException: java.net.SocketException: Connection reset
by peer: socket write error
Posted by Jörg Heinicke <Jo...@gmx.de>.
Hi Paul,
this usually happens if the client canceled the request, e.g. by clicking 'Stop' while the page is still being loaded.
Regards,
Joerg
-------- Original-Nachricht --------
> Datum: Wed, 18 Nov 2009 06:32:58 -0500
> Von: Paul Joseph <pj...@gmail.com>
> An: users@cocoon.apache.org
> Betreff: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
> Hi There,
>
> On one particular request, I get a ClientAbort exception, connection
> reset error (see below.) Any reason why this could be?
>
> I use Tomcat Is there a socket timeout configuration for Tomcat 5.5
> and Cocoon 2.1.11.
>
> I have seen a similar thread, but with no resolution.
>
> thx.
> Paul
>
> The error is as follows:
> WARN (2009-11-17) 10:58.04:991 [access]
> (/array/webtask/request/reqMine) http-9090-Processor18/CocoonServlet:
> ClientAbortException: java.net.SocketException: Connection reset by
> peer: socket write error
> ERROR (2009-11-17) 10:58.25:037 [flow] (/array/webtask/request/reqMine)
> http-9090-Processor23/NativeJavaMethod: java.lang.IllegalStateException:
> getAttribute: Session already invalidated
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org