Oracle BPEL – Wait Activity Stuck or Hanging – Never Returns to Console

Posted on May 3, 2008 in Technical Tips | 0 comments

This is a very, very common complaint I hear from Oracle BPEL developers, testers, and production support.

I find there are a couple reasons that this can happen:

1. The flow has faulted sometime after the wait activity, but never dehydrated again, so it appears to be “stuck” on the wait activity. Put in some more waits to force dehydration soon after your “problematic” wait to ensure the wait really isn’t your issue.

2. In 10.1.3, the default wait in JDev is set to 1 day; please, be sure to set your wait times properly.

3. The flow really is just waiting too long. Oracle advertises the wait time as a “minimum”. You may want to increase the number of threads you have running for your scheduler.

• Stop your application server
• Take a backup copy of the following file:
  
  \bpel\domains\[domain-name]\config\resources-quartz.properties
• Change the resources-quartz.properties file:
  
  com.oracle.bpel.expirationAgent.threadCount is defaulted to 10. You can increase this to 50 or 100, or more depending on your load.
• Restart the application server

Please, drop us a quick comment below if this helps.

Related Information:

1. Asynchronous vs Synchronous BPEL Processes

   Asynchronous and Synchronous BPEL processes,...

2. Oracle BPEL Sensors for Real Time Event Publishing from Business Processes – A Design Perspective

   This article is a look...

3. Oracle BPEL Email Notification – Remove Attachment

   If you have used the...

4. Oracle BPA -> BPEL Manual Configuration Items

   Oracle BPA does a great...

5. Oracle SOA Environment Performance Tuning Options – Quick Notes

   Tuning OAS and BPEL Console....

6. BPEL

   Following are a few of...

7. Oracle AS: Undeploying Multiple Applications (including BPEL Human Tasks)

   Undeploying a single application in...

8. BPEL Not Good For Rapid Changes

   I am excited about BPEL’s...