My Oracle Support Banner

Asynchronous Call to PL/SQL Program is Timing Out Waiting on Response (Doc ID 943000.1)

Last updated on AUGUST 10, 2018

Applies to:

Oracle SOA Platform - Version to [Release 11gR1]
Oracle(R) BPEL Process Manager - Version to
Information in this document applies to any platform.
Information in this document applies to any platform.


You have a long-running PL/SQL program.
You have heard that to avoid a JTA transaction timeout, you can configure a BPEL process as follows:

- do not set "My Role" when configuring the database adapter partnerlink
- do not create an output variable for the invoke activity

This is supposed to force BPEL to asynchronously call the PLSQL program and immediately continue
with the next BPEL activity.
But this configuration instead is causing the invoke activity to wait on a response from the
PL/SQL program until it eventually times out.
Even with the nonBlockingInvoke property set to 'true' for the database partnerlink, the issue


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.