Retry Mechanism in BPEL

Hi,
Following is our requirement:
Suppose BPEL process has 10steps , while exectuing step 6 it got exception and we stored in JMS Q. Then after sometime we are re-starting this BPEL process , then it shud start execution from step:6.
Is this possible in BPEL ?
If it is possible , how can we implement it?
How can we revoke all the activities performed in previous steps [In this case , How will we revoke the activities performed till step:5]?
Pl let me know if you any solution for this.
Regards,
Chaitanya

fault policy framework supports the rethrow activity, so after updating the payload (human activity from fault policy framework) you can rethrow it and trigger the process again with the updated payload.
but you see where it ended last time and skip the steps in front of it, you need some sort of custom audit trail which you update during the process
and before every step in the process you check this payload to see whether or not last time it passed this step
so after finishing step1 you update with payload with laststepcompleted=1
then in front of this step you do some check on if laststepcompleted >= 1 then skip this one
and do that for every step
or someone else must have a smarter solution :)

Similar Messages

Error handling and Manual Retry mechanism in BPEL

Hi Gurus,
We have a requirement that If any error occurs during BPEL process , We need to auto retry. if auto retry is not enough We need to manual retry and send the request message to Worklist for retry.
In our BPEL process We have CreateOrganization API provided which can not be rollback using compansation handlers. From Here I need to intiate the process using worklist if any error.
I dont know how to intiate the process from particular node. Please help me.
thanks,

My process has 5 invoke activities
CreateOrganization
createFaxNumebr
CreateAddress
CreatePhone
CreatePhExt
In my process , the first 2 services gets success, 3rd one 'CreateAddress' fails due to DB connection is broken. I can not rollaback first 2. I want to retry 3 rd using worklist when DB connection is fixed. I dont know how to call CreateAddress partner link as Catchall branch is not in scope of 'CreateAddress' and resume the process to execute 4 and 5 services.

Retry mechanism in Fault handling framework SOA 11g

hi
i have used Fault management framework in my project. I have added fault-policies and fault-bindings file. in fault-policies file i am using retry mechanism for any remote or binding fault. but i am not able to see the retry working in flow trace. however human intervention and terminate actions are working fine.
can any one assist me why retry mechanism is not working.
thanks in advance.

hi
thanks for the response. i added that property in my bpel tag but unfortunately it didn't work. plus the instance remains in running state. plz help me out with this.
this is my fault-policies.xml and fault-binding.xml
fault-policies.xml*
<?xml version="1.0"?>
<faultPolicies xmlns="http://xmlns.oracle.com/CreateTaskPOC_jws/Project9/BPELProcess1">
<faultPolicy version="2.0.1" id="MyCompositeFaultPolicy">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:bindingFault">
<condition>
<action ref="ora-retry"/>
</condition>
</faultName><faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-retry"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-rethrow-fault"><rethrowFault/></Action>
<Action id="ora-retry">
<Retry>
<retryCount>3</retryCount>
<retryInterval>2</retryInterval>
<retryFailureAction ref="ora-rethrow-fault"/>
</Retry>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
fault-bindings.xml
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1" xmlns="http://xmlns.oracle.com/CreateTaskPOC_jws/Project9/BPELProcess1">
<composite faultPolicy="MyCompositeFaultPolicy"/>
<component faultPolicy="MyCompositeFaultPolicy">
<name>BPELProcess1</name>
</component>
<reference faultPolicy="MyCompositeFaultPolicy">
<name>InsertEmp_BPELProcess</name>
</reference>
</faultPolicyBindings>

SOA11g retry mechanism

Hi
i am using SOA11g & weblogic server10.3.2. I have built synch bpel process which keeps retrying for 3 times if there is quite delay in response. I have not mentioned any retry mechanins in my BPEL. Could you please suggest me is there any setting on server which i need to change to avoind this retry??
Thanks
Amit

The BPM will then be in retry mechanism mode let say 5 attempts or 5 hours
Your scenario is: SYS1 > BPM <> SYS2 ....and rest of processing
Your question is if BPM <--> SYS2 communication fails in first attempt
So the above step will be SYNC.....include a BLOCK with an Exception Branch in your BPM....if the SYNC steps fails then the Exception Branch will be triggered....now in the exception branch include a WAIT step (set the time accordingly...avoid setting it for a big time interval),
After the WAIT step include a SYNC-Send step which will again send the same message (BPM <--> SYS2) .....check if you get the response or still in error....if in error then implement a proper error handling.
Just ensure that the wait step does not make the BPM wait for too long
Regards,
Abhishek.

Retry Mechanism for BPM in PI 7.1

Hi Experts,
Is it possible to have a retry mechanism in implementing BPM on a solution? Here's my scenario:
With BPM initial scenario:
Sending system sends a message to PI and will be routed to another system (let's say a Master Data System) via BPM to get a specific data that will be included on the initial data that was sent to from a sending system. The BPM then handles the mapping of that specific data and then sent to a Receiving System.
Additional Scenario (if it is possible):
What if the Master Data System is down?!
- an additional BPM will be added to the initial BPM and the purpose is solely for retry mechanism. The BPM will then be in retry mechanism mode let say 5 attempts or 5 hours..and if it successful then the initial scenario will push..but if the system is still down, and retry mechanism reached its limit then it will send will throw an error or an alert.
If this is possible, how can this be handled?
Appreciate your response with this. Thanks!
Cheers,
R-jay

The BPM will then be in retry mechanism mode let say 5 attempts or 5 hours
Your scenario is: SYS1 > BPM <> SYS2 ....and rest of processing
Your question is if BPM <--> SYS2 communication fails in first attempt
So the above step will be SYNC.....include a BLOCK with an Exception Branch in your BPM....if the SYNC steps fails then the Exception Branch will be triggered....now in the exception branch include a WAIT step (set the time accordingly...avoid setting it for a big time interval),
After the WAIT step include a SYNC-Send step which will again send the same message (BPM <--> SYS2) .....check if you get the response or still in error....if in error then implement a proper error handling.
Just ensure that the wait step does not make the BPM wait for too long
Regards,
Abhishek.

BPEL and retry mechanism

What does BPEL PM offer with regard to QoS provisions w.r.t partner invocations eg if my attempt to invoke a partner WS fails, can I specify a number of retries?

Each BPEL PM node includes a recovery agent. The recovery agent wakes up periodically and queries the dehydration store for work that should have been scheduled to be performed and has not be performed yet. For reducing lock contention, we recommend to run the scheduled recovery on one node of the cluster only and manually reprogram another node to become the recoverer if the existing recoverer goes down. -Edwin

Error Handling mechanism in BPEL Console

Hi
One of our client wanted to handle the situations where a BPEL Instance at BPEL console got errored for different reasons.
We Know that we can handle all possible error combinations with in a BPEL. But, here client requirement is because of any reasons (May be not problem because of any BPEL code) if BPEL Process Instance will complete with error in BPEL Console how do we handle those errors. Do, we have any control on BPEL console.
Please do share your experience on this requriement.
Regards
Kiran Akkiraju

I have tried to chain two conditions when a remote fault occurs, as described in the links suggested.
ora-retry and then ora-human-intervention.
But only the last condition is executed, in this case it is the human-intervention. The retry is definitively not executed.
If I do the other way around human then retry, only retry is executed.
Does someone has the same issue?
Extract from DefaultPolicy.xml:
     <Conditions>
          
          <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
               <condition>
                    <action ref="ora-retry"/>
               </condition>
               <condition>
                    <action ref="ora-human-intervention"/>
               </condition>

Configure the Retry Mechanism of PI

Hi All,
As per my knowledge, if the receiver system is down in the landscape then PI retries for 3 tiimes in a gap of 5 min each and then gives a SystemError message.
I want to know that can I configure this setting?
I have an IDoc to HTTP scenario and I want to configure the number of times the retry should happen before error message.
Also is it possible that whenever the receiver system comes up, the messages be resent to it automatically?
regards,
Piyush Mathur

Hi Piyush,
You can change the default retry interval value from 3 to any.
Goto Communication Channel monitoring> Select the Communication channel>Below you will find Setting Tab>Click on Overwrite button of MaximumNumber> Then change the default value.
Check the link suggested by Shabarish....
>>>Also is it possible that whenever the receiver system comes up, the messages be resent to it automatically?
Yes, in between the retry interval if the receiver system in Up then the files will be automatically processed to the receiver system.
Thanks,

Retry mechanism for HTTP Transport in OSB

Hi
I am using OSB 11gR1. I have a business service which is HTTP protocol based.
The BS is configured with the RetryCount as 0 and Retry Application Errors is enabled.
I have to store the message in a persistent store or some store in case the endpoint URI is temporarily unreachable.
Once the URI is reachable, the service should pick the data from the data store and send it across to the HTTP URI.
Has anyone implemented this or knows how this can be configured?
Please suggest and help.
Regards
Kshama

Business Service by default does not have any persistence available(well apart from persistence used for throttling which is not useful for this use case).
You will need to add an explicit persistence layer between the Proxy Service which receives the message from Client and the HTTP Business Service which calls the back end service provider.
You will need a JMS queue and additional JMS Business Service and a JMS Proxy Service in the flow.
The flow should now look like following:
Client-->HTTP PS-->JMS BS-->JMS Queue-->JMS PS-->HTTP BS-->service provider
You can set retry conditions on the XA enabled JMS queue so that it will keep retrying the messages which failed because destination was unreachable until they are delivered. You will be able to set a retry delay and maximum number of retries etc. Keep in mind that this would be an asynchronous flow.

Retrying faulted BPEL instances from Oracle BAM.

Hi
need to configure bam report by adding hyperlink to order id of the faulted BPEL process to open em console to retry the faulted BPEL instances.
Oracle document available is wrt BPEL 10g where we configure static address of the BPEL console activity tab and pass dynamically the faultID by defining action in BAM report.
I am not able to configure the static address and dynamic link wrt soa 11g.
Please help me in achieving this functionality using BAM report for BPEL 11g.
Thanks in advance
Krishna

the locator api + the instance state will do the trick (the console is using those btw.). Various resources on the net explain this in depth (including the developers guide)
thanks

Retrying partner link in soa suite 11g

how do i retry the partner link invoking webservice if it fails

you could add the property on the invoke of the partnerlink
http://otndnld.oracle.co.jp/document/products/as10g/1012/doc_v3/integrate.1012/B14448-01/html/appx_deploydesc.htm
Table D-2 Configuration Properties for the partnerLinkBinding Deployment Descriptor (retry*)
Or configurate it with the fault policy framework
http://www.it-eye.nl/weblog/2007/09/10/oracle-bpel-10133-fault-policy-management/
retry in 11g
Retry Mechanism in BPEL

Remote Fault Auto Retry and Notification

Hi,
I am using Oracle SOA Suite 11g PS2.
In one of the process I am trying to use Fault handling mechanism of SOA.
I have written code to use Auto Retry mechanism using fault-policies.xml,I want to send notification before SOA start Auto Retry on Remote Fault.
It does not execute catch block but it directly start Auto Retry.
Code of my fault-policies.xml is as follows
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="Test"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-rethrow-fault"/>
</condition>
<condition>
<action ref="ora-retry"/>
</condition>
</faultName>
</Conditions>
<Actions>

<Action id="ora-retry">
<retry>
<retryCount>1</retryCount>
<retryInterval>120</retryInterval>
<retryFailureAction ref="ora-human-intervention"/>
</retry>
</Action>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
<Action id="ora-rethrow-fault">
<rethrowFault/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
I want to send notification before SOA start Auto Retry.
anyone aware why it does not rethrow fault and then starts Auto Retry.
Thanks,
Arun Jadhav.

Any help ?

BPEL, clustering and fail over

How is failure of a BPEL PM node monitored so that in-flight processes can be automatically restarted on one of the surviving PM nodes?

BPEL PM has a built-in retry mechanism and end-point load balancing:
<partnerLinkBinding name="RatingService">
<property name="wsdlLocation">
http://localhost:8080/axis/services/RatingService1?wsdl
http://localhost:8080/axis/services/RatingService2?wsdl
</property>
</partnerLinkBinding>
<partnerLinkBinding name="FlakyService">
<property name="wsdlLocation">http://localhost:8080/axis/services/FlakyService?wsdl</property>
<property name="location">http://localhost:2222/axis/services/FlakyService</property>
<property name="retryCount">2</property>
<property name="retryInterval">60</property>
</partnerLinkBinding>
Please refer to the Resilient Flow Demo for more information, packaged in the product and documented on OTN, for more information:
http://www.oracle.com/technology/products/ias/bpel/htdocs/orabpel_technotes.tn007.html

Composite continuously filling logs with endless retrying

Hi All,
I had a composite to enqueue the message into MQ using native MQ Adapter. Everything was working fine till one day when suddenly network connectivity to the MQ was lost due to firewall changes. As no connection could be established by the composite, I started getting Connection Timeout exceptions in the logs. Since then it's filling the logs continuously. How do I stop it?
I deleted the JNDI from Weblogic, tried shutting down the composite, changed the JNDI hosts to blank but all in vain.
Could you please tell what's happening behind the scenes?
- SOA Suite 11.1.1.5
- Simple BPEL composite
- Synchronous process with just enqueue operation
Regards,
Neeraj Sehgal

Hi,
Sorry for delay. I tried undeploying also. Later I went ahead and removed the host from the weblogic JNDI to prevent it from trying the connection, but after that the error changed to below.
<div class="jive-quote">
[2012-07-20T03:54:26.950-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@19c2817f] [userId: ohsadmin] [ecid: 79c1912e960c7e6d:-1ffd1268:1375b34bd87:-8000-0000000000593a78,0] [APP: soa-infra] MQSeriesAdapter InsertMessageIntoMQ:EnqueueMessageInMQ [ Enqueue_ptt::Enqueue(opaque) ] [QueueProcessor] Exception caught in while loop
[2012-07-20T03:54:26.950-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@19c2817f] [userId: ohsadmin] [ecid: 79c1912e960c7e6d:-1ffd1268:1375b34bd87:-8000-0000000000593a78,0] [APP: soa-infra] MQSeriesAdapter InsertMessageIntoMQ:EnqueueMessageInMQ [ Enqueue_ptt::Enqueue(opaque) ] [[
javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/MQ/BBW_MAXIMO_CORE from JNDI and get a new Connection Handle.
at weblogic.connector.outbound.ConnectionManagerImpl.checkIfPoolIsValid(ConnectionManagerImpl.java:442)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:109)
at oracle.tip.adapter.mq.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:120)
at oracle.tip.adapter.mq.inbound.QueueProcessor.checkForNewConnection(QueueProcessor.java:218)
at oracle.tip.adapter.mq.inbound.NonManagedQueueProcessor.startTransaction(NonManagedQueueProcessor.java:51)
at oracle.tip.adapter.mq.inbound.QueueProcessor.run(QueueProcessor.java:245)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
</div>
I further deleted the JNDI too, but still the above error is filling the logs. I think it's some sort of retry mechanism that is continuously trying to connect. But there is no process, no JNDI currently but still it's retrying.
Please help me stop this.
Regards,
Neeraj Sehgal

Foreign JMS Server Persistance\Retry in case Remote JMS Provider goes down

Hi All
I would need more clarity on this. How does the Foreign JMS Server behave in case the remote JMS provider goes down. Does it take the message from the Publishing Proxy Service and retries\persists the JMS Message till the remote provide is up?
Please let us know. This would effect our design as retrial is very important here. Thanks

If you want to provide guaranteed delivery with automatic retries when using remote JMS implementations, there are multiple ways to implement it:
1. While reading from a foreign JMS destination
Create a Foreign JMS server using transactional drivers (use XA in case of JMS). The messages remain on remote server JMS queue and OSB proxy polls the message directly on remote server. So if Remote Server is down OSB will not be able to read the message. Once remote server is up OSB will pick up the message (as long as foreign JMS server provides persistence and maintains the messages in the queue during a server restart). In case of error in OSB foreign queue can do retry if it provides a retry mechanism.
2. While writing the message to a foreign JMS destination
a. Use a foreign JMS server using transactional connection. Put the retry mechanism in OSB Business service which writes to the foreign JMS/MQ queue. In case of failure Business Service can retry based on configuration. If you want to provide guaranteed delivery then create a local JMS queue to store the messages. So when remote destination is down for a long time undelivered messages will be rolled back to the local queue. You can put retry mechanism on the local queue.
b. Use a messaging bridge which will write the messages to the remote destination. You can configure retry delivery rules in messaging bridge so once busienss service writes the message to the bridge, a SAF agent will ensure the delivery to remote destination whenever it is up.

Retry Mechanism in BPEL

Similar Messages

Maybe you are looking for