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!

Waiting for response has timed out

906470May 8 2012 — edited Feb 26 2020

BPEL ROCESS NAME : WshSendTxnToOtmService BPEL INSTANCE ID : 773933 ERROR CODE : remoteFault ERROR MESSAGE: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage} parts: {{ summary=Waiting for response has timed out. The conversation id is urn:A32BDDC095F611E1BFD083E5BFCC83D0. Please check the process instance for detail. ,detail=Waiting for response has timed out. The conversation id is urn:A32BDDC095F611E1BFD083E5BFCC83D0. Please check the process instance for detail. ,code=0} DATE & TIME: 2012-05-04T10:47:20

We have already change these settings in SOA as well as in EBS instances

Distribution_Lock_timeout changed from 60 to 300

Changes done is SOA Server:

These are the current settings in SOA for the following properties: syncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout
120<780<900

If we increase the Current settings which are mentioned below does this Solve this Timeout Error?
syncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout
240<1800 (30 minutes)/ (<3600 (1 hour)

Thanks,
K

Edited by: 903467 on May 8, 2012 1:28 AM

Locked Post

New comments cannot be posted to this locked post.

Locked on Jun 6 2012

Added on May 8 2012

#business-process-management-suite, #soa-process-management

2 comments

1,676 views