This discussion is archived
1 Reply Latest reply: Dec 4, 2012 8:15 PM by RK.. RSS

Big Problems after undeploying old processes via BPEL Console

973931 Newbie
Currently Being Moderated
Have logged a call but this is a big issue for us so pitching it out here just in case...

We have had a BPEL 10.1.2 solution running in production now for 6 years. Recently we deployed some new versions of a number of the processes. As part of the deployment we undeployed, via the BPEL Console, the old processes. My expectation was that this would mark any old instances as stale and I would be able to clear these up via the Instances tab.

What we are seeing now is a crippled system. On startup there are lots of messages logging:

Error while invoking bean "activity manager": Missing process for instance.
The process ("XXXXXXXXXXXXXXl", revision "1.0") for instance "17893471" was not loaded by the domain; the instance will now be marked as stale.
The archive for process "XXXXXXXXXXXXXX", revision "1.0" may have been deleted from the domain manually; in this case the domain would not have been able to mark all instances belonging to the process as stale.

and then a short while afterwards we see endless timeouts and rollbacks:

<2012-11-13 05:09:06,181> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:873)
     at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleRecover(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1665)
     at com.collaxa.cube.engine.dispatch.message.domain.RecoverMessageHandler.handle(RecoverMessageHandler.java:36)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)


and

<2012-11-13 03:00:21,043> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002

Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.process.StaleMessage"; the exception is: Transaction was rolled back: timed out;


Any ideas ? We tuned all out timeout setting years ago but whatever BPEL is trying to do with the 'orphan' instances looks very slow.

RJ.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points