Oracle BPEL Error: SOAPException: javax.xml.soap.SOAPException: Message send failed: Read timed out
Received the following error in the Oracle BPEL composite. The BPEL Web Service adapter throws the following error while calling one of the Oracle Primavera Web Services.
We have the following errors in the SOA_SERVER.OUT log file
<Error> <oracle.integration.platform.blocks.soap> <BEA-000000> <Unable to dispatch request to http://HOST/p6ws/services/ProjectService due to exception
javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Read timed out
Caused By: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Read timed out
Caused By: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
From the above Error log, it clearly shows the BPEL Webservice client waited for some time for the server response and throws Timeout error once it reached the time limit. Adding the following BPEL WS adapter properties help this issue. The WS client waits unlimited time till the server response. But we need to analyze on the server side as well. Why the server takes much time to respond back. It might be Out of Memory, CPU full, Proxy issue, Load balancer, low session timeout or other.
Oracle.webservices.httpConnTimeout => 0 (Number in Millisecond, 0 means unlimited)
Oracle.webServices.httpReadTimeout => 0 (Number in Millisecond, 0 means unlimited)
The views expressed on this blog are my personal views and do not necessarily reflect the views of my employer.
Please feeling free to reach me on any comments and feedbacks you have. Would be more than glad to listen and reply 🙂
Latest posts by Govind
- Is it possible to logout Primavera P6 through SQL Query? - February 16, 2018
- How to Create Primavera P6 EPPM Database schemas in Microsoft SQL Server - February 15, 2018
- Configure Windows Firewall for Microsoft SQL Server 2017 – Part 4 - February 14, 2018