BPEL while deploying get error Lock or Activation

Hi,

People generally face issue while deploying BPEL "Activation error". This issue arises when AQ or JMS adapter being used in your flow and while trying to deploy on server it validates the availability of resources. But when it can not find it just throws either activation error based on resources.

I would say, Go to BPEL console and expire the state and make it inactive. Then deploy it again. Still it doesn't resolve then try to check the JNDI Adapter resource if that is available.

For Lock Error:
Error while invoking bean "process manager": Timed out waiting for process load
lock.
Failed to obtain load lock for process "test_debmas01-1.0"; timed out after

Increase the lock timeout value through the Java system property
orabpel.process.lock.timeout. This property can be set from the OPMN
start command by specifying -Dorabpel.process.lock.timeout=300 (the
unit is seconds).

If you still receive a lock timeout even with extremely large timeout values, a
writer thread is most likely stuck. To determine what the writer thread is doing,try to obtain several thread dumps while the readers are blocking attempts to
acquire the lock.