Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Software caused connection abort: recv failed

676500Dec 19 2008 — edited May 12 2010
Hi All,

I've got the following architecture: one web-service on Axis2 (which just send current time back) and one simple BPEL process (synchronous, two-way operation), that just invoke first web service on Axis2. Axis2 container (axis2.war) is deployed to Oracle AS 10g to home instance.

When i install patchset for SOA 10.1.3.3.0 everything works fine (no recv faild errors), but when i install patchset 7272722 for SOA 10.1.3.4 i have some times following error (during BPEL - Axis2 interaction, i.e. when BPEL call Axis2 service):

<2008-12-19 13:42:08,625> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": faultName: {{http://sch
emas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{summary=<summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: jav
ax.xml.soap.SOAPException: Message send failed: Software caused connection abort: recv failed</summary>
}}

If i call Axis2 service, for example, using soapUI (simple WS client) i have no such errors.

I also try to configure BPEL domain (increase dspEngineThreads, dspInvokeThreads, dspSystemThreads), also try to increase diferent timeouts, but this doesn't help.

Please, can anyone help me in solution of this problem?!
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 9 2010
Added on Dec 19 2008
2 comments
6,013 views