BPEL Process Using a File Adapter With the minimumDelayBetweenMessages Property Gets Turned Off Automatically By BPEL (Doc ID 1306126.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.5.0 and later
Information in this document applies to any platform.
***Checked for relevance on 21-Feb-2013***

Symptoms

In 10g SOA you have a polling file adapter, this activates fine, then is de-activated after some time, during the processing of a file, this sets the BPEL process state to OFF. The BPEL process then has to be turned back on manually from the BPELConsole for the adapter to pickup files again.

The File Adapter has defined the "minimumDelayBetweenMessages" property in the activation agent in the bpel.xml file, for example as follows:

<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent"        partnerLink="inboundFile">
<property name="retryInterval">5</property>
<property name="retryMaxCount">5</property>
<property name="portType">Read_ptt</property>
<property name="minimumDelayBetweenMessages">2550</property>
<property name="rejectedMessageHandlers">file:///u01/oracle/product/10.1.3.1/OracleAS_1/error</property>
</activationAgent>
</activationAgents>


The use of  minimumDelayBetweenMessages may have been chosen since the "Files contain multiple messages" option was chosen in the Adapter Wizard in JDeveloper.

 



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