Article

Error 140 when running client during response to web request

« Go Back

Information

 
EnvironmentProgress 9.x
OpenEdge 10.x
UNIX
Question/Problem Description
Error 140 when running client during response to web request
** Pipe to subprocess has been broken. (140)
4GL client runs to deliver data as web request response
HTTP request is canceled by client before response is fully transmitted
Clarifying Information
Error Message** Pipe to subprocess has been broken. (140)
Defect/Enhancement Number
Cause

When the HTTP client cancels a request, the web server in charge of the request will shut down the communication socket with the process in charge of providing the data for the request response.

If a Progress 4GL client was in charge of providing the response, it will receive SIGPIPE when attempting to write more data to the socket after it has been shut down. This is expected behavior.

Resolution

To prevent the error message, the users should avoid the following:

- close the web browser window before the response is fully displayed,

- navigate to a different page before the current page is completely loaded,

- cancel a request (such as using the "close" button).

Workaround
Notes
This situation is to be expected when using the regular Progress client as part of an application logic that answers web requests; it can usually be ignored since error 140 will cause the client to terminate gracefully.
Attachment 
Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful.



Characters Remaining: 255

 



Copyright © 1993-2014. Progress Software Corporation. All Rights Reserved. See the next generation of application development and data connectivity software, try now!