ORA-03111: break received on communication channel
sameer hDec 22 2010 — edited Jun 19 2012Hi
I am using OSB 11g and invoking oracle stored procedure through db adapter. In production environment, we are getting "ORA-03111: break received on communication channel" in AdminServer.log intermittently.
<BEA-381971> <Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/cm.cpm_1.0/resources/interfaces/getInvoiceHistory [ getInvoiceHistory_ptt::getInvoiceHistory(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'getInvoiceHistory' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the SSB_USER.VF_SELFCARE.GETINVOICEHISTORY API.
An error occurred while preparing and executing the SSB_USER.VF_SELFCARE.GETINVOICEHISTORY API. Cause: java.sql.SQLException: ORA-03111: break received on communication channel
; nested exception is:
BINDING.JCA-11811
Stored procedure invocation error.
Error while trying to prepare and execute the SSB_USER.VF_SELFCARE.GETINVOICEHISTORY API.
An error occurred while preparing and executing the SSB_USER.VF_SELFCARE.GETINVOICEHISTORY 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. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
Has somebody faced this issue before. This error comes randomly and results in lot of failed transactions. I have tried googling for this issue but no specific explanation. We have tried increasing the SDU size in listener.ORA as given in one of the Oracle support guide but of no use.
Any help in this regard is greatly appreciated.
Thanks,
Sameer