AQ JMS Adapter Initiating ESB Flow Stops Processing Messages After a Network Interruption

(Doc ID 1276222.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle SOA Platform - Version 10.1.3.3.0 and later
Information in this document applies to any platform.

Symptoms


ESB intermittently stops dequeuing / processing messages after a network interruption.
The problem might be accompanied by the following errors:

Error 1
---------------------------

<PAYLOAD>
<MSG_TEXT>ServletException cause</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[com.evermind.server.http.HttpIOException: Connection reset by peer
at com.evermind.server.http.EvermindServletOutputStream.write(EvermindServletOutputStream.java:210)
at com.evermind.server.http.EvermindJSPWriter.writeOut(EvermindJSPWriter.java:539)
at com.evermind.server.http.EvermindJSPWriter.jspflush(EvermindJSPWriter.java:436)
--------------------------------
In this case oc4j works as a server and the error message indicates that the client has disconnected.
-------------------------------

Error 2
-----------
<PAYLOAD>
<MSG_TEXT>WSIF invocation failed while invoking RemoteProcessManager:createProcessInstance{http://host:port/ProcessService.wsdl} and endpoint location = </MSG_TEXT>
<SUPPL_DETAIL><![CDATA[org.collaxa.thirdparty.apache.wsif.WSIFException: exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Premature EOF encountered
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1717)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1463)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation
--------------------------
In this case oc4j is a client calling http://host:port and is disconnected.
----------------------------

Error 3
-----------
<MSG_TEXT>Could not send the activity messages. Current internal buffer size is "1"
oracle.tip.esb.server.dispatch.QueueHandlerException: Error publishing jms message

at oracle.tip.esb.server.dispatch.JMSEnqueuer.enqueue(JMSEnqueuer.java:401)
at oracle.tip.esb.monitor.agent.ActivityMessageBatcher.sendXML(ActivityMessageBatcher.java:424)
at oracle.tip.esb.monitor.agent.ActivityMessageBatcher.sendMessages(ActivityMessageBatcher.java:358)
at oracle.tip.esb.monitor.agent.ActivityMessageBatcher.run(ActivityMessageBatcher.java:341)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.jms.AQjmsException: ORA-12152: TNS:unable to send break message

at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1180)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1254)
at oracle.j2ee.ra.jms.generic.TopicPublisherWrapper.publish(TopicPublisherWrapper.java:65)
at oracle.tip.esb.server.dispatch.JMSEnqueuer.enqueue(JMSEnqueuer.java:399)
... 8 more
</MSG_TEXT>

SUPPL_DETAIL><![CDATA[oracle.jms.AQjmsException: ORA-03114: not connected to ORACLE

at oracle.jms.AQjmsSession.preClose(AQjmsSession.java:971)
---------------------
This error points to AQ JMS client disconnecting from a database.
---------------------

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