Processing an instance hangs for 30seconds or more before executing when one of the nodes is down (Doc ID 1231195.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 6.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 14-May-2012***
***Checked for relevance on 23-October-2013***

Symptoms

You may see a 30 second delay or longer between the time an activity starts to execute , until the time it actually does execute. If you have cluster logging enabled you may see some messages like this:

We see the following messages:
Cluster (getLocalCount) invocation.
(30 seconds later)

Cluster (getLocalCount) Reponse: sender=SERVER1, retval=0,
received=true, suspected=false
Cluster (getLocalCount) Reponse: sender=SERVER2, retval=0,
received=true, suspected=false
Cluster (getLocalCount) Reponse: sender=SERVER3, retval=1,
received=true, suspected=false
Cluster (getLocalCount) Reponse: sender=SERVER4, retval=null,
received=false, suspected=false
Cluster (getLocalCount) Reponse: sender=SERVER5, retval=null,
received=false, suspected=false
Cluster (getLocalCount) Reponse: sender=SERVER6, retval=null,
received=false, suspected=false
Loading instance /UserProcess#Default-1.0/12345/0

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