Project

General

Profile

WSS_timeout606.txt

Robert Weekly, 10/30/2014 08:55 AM

 
1
+Behavior using SLEEP FIRST handler+ 
2
* a 500 error is produced in the browser window with the following text: @Error 500: Timeout or unexpected termination of handler,  exit code: 143  error: none, message is zero length@
3
* in dataselect.log, the following error is shown in the stack: @ERROR ProcessStreamingOutput  - stopProcess called for timeout or exception, outputStream is null, this indicates the handler never wrote data.@
4
* from the JMS broker: @...,error_type=killit was called, possible timeout waiting for data after intial data flow started,...@
5

    
6
+Behavior using TEXT FIRST handler+
7
* No error is shown in the browser window (indicative of HTTP 200 code)
8
* in dataselect.log, a different error from before: @ERROR ProcessStreamingOutput  - stopProcess called for timeout or exception, an error message is being appended to the output stream before killing the handler.@
9
* from JMS broker: @...,error_type=killit was called, possible timeout waiting for data after intial data flow started,...@