Troubleshooting: Save or Submit work, Internet Explorer cannot display the Web page (Oracle WebLogic Server)
When processing a work object from the Web, you click Save or Submit, but PRPC will continue to process the work, and will eventually display the error message:
Internet Explorer cannot display the webpage or
HTTP:404 Page Not Found. This error occurs erratically, reported by some users for some work objects but not all work objects. Some work objects can be saved or submitted, others cannot. The Tracer detects all work being processed, but once the work is saved or submitted, the Tracer shows no processing.
Analysis of the deployment environment reveals an issue with the configuration of the WebLogic Server Proxy Plug-ins, specifically the Web Server timeout setting configured on the Apache HTTP server WebLogic plug-in file.
A long-running request submitted to the server with the client waiting for the response causes the server to be busy at that time. The client never gets the response from the server because the Apache Web Server WebLogic plug-in is set to intercept that long-running request and terminate as specified by the timeout setting WLIOTimeoutSecs on the Apache HTTP server WebLogic plug-in file. The reason for the long-running request could be the amount of data submitted to the server, pxInputDBbytes and pxOutputBytes, or the database SQL query and BLOB reads.
To correct and prevent this problem from occurring, check the WLIOTimeoutSecs (formerly known as HungServerRecoverSecs) parameter value for your Web Server WebLogic plugin. See the Reference for complete information about all WebLogic Web Server plug-in parameters.
If a long-running PRPC requestor takes longer than specified by the parameter WLIOTimeoutSecs (or HungServerRecoverSecs), you may see no server response from the client side because of the short interval timeout value specified for WLIOTimeoutSecs (or HungServerRecoverSecs) in your Web Server plug-in file. Increase this parameter value to accommodate long-running requestors as necessary. For example, if the long-running requestors take five (5) minutes to complete, then set the parameter value to be longer than 300 seconds (five minutes).