Oracle Technology Adapter Periodically Throws Error: ORA-03111: break received on communication channel (Doc ID 1219453.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle SOA Platform - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 08-Mar-2012***
***Checked for relevance on 09-August-2013***

Symptoms

Whilst using SOA 11.1.1.3 you randomly receive error "ORA-03111: break received on communication channel" when using an Oracle Technology Adapter that interfaces with a database using the JDBC thin driver.  The adapter could be configured to use any of: Database, AQ, Oracle Applications, or AQ-JMS.

A similar error will be seen in the logfile at $MIDDLEWARE_HOME/user_projects/domains/base_domain/servers/soa_server1/logs/<SOA Managed Server Name>-diagnostic.log (this example is from the use of an Oracle Applications Adapter):

[2010-08-27T11:43:57.826-04:00] [WLS_SOA1] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.invoke.pool-4.thread-21] [userId: <anonymous>] [ecid: 0000Iek3L0d7u1x5KBnZ6e1CTKti000MHn,0:1:0x5f62391:1:0x5f62392:1:0x5f62393:2:0x5f623b4:2:0x5f623b9:1:0x5f5e7c6:1:0x5f5e818:1:100001817] [APP: soa-infra] [composite_name: EOP102_releaseProductionOrder] [component_name: Order] [component_instance_id: 9845446] JCABinding=> Order:Provide [ Provide_ptt::Provide(InputParameters,OutputParameters) ] Could not invoke operation 'Provide' against the 'Oracle Applications Adapter' due to: [[
BINDING.JCA-11811
Stored procedure invocation error.
Error while trying to prepare and execute the APPS.XOPS_ITEM.ITEM API.
An error occurred while preparing and executing the APPS.XOPS_TEM.ITEM API. Cause: java.sql.SQLException: ORA-03111: break received on communication channel

Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered retriable, likely due to a communication failure. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml).

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms