Faulted Instances - Recovering

[bsethuramalinga]

Hi,

I have BPM Process with 'UserTask', deployed into Activiti Engine.  When I start the business process, the instance is created and for some reason it gets closed. I believe some error is forcing the instance to be closed right away. please advise how to debug Activiti Engine.

Thanks

[sebastian_s]

Hello bsethuramalingam,

you did not provide a lot of information but just a very general description of your problem. Can you write a unit test demonstrating your problem and can you post it here?

There's a sticky post in this part of the forums which explains how to write a unit test.

Bye!

[bsethuramalinga]

is there a way to identify faulted instances in Activiti Explorer. Commercial products like Oracle SOA Suite, had an extensive features in managing the instances of BPEL Process. I was looking for similar feature in Activiti. I understand that Oracle SOA Suite and Activiti are of two different platforms serving different purposes. SOASuite is for BPEL and Activiti is for BPM.  In my opinion, Activiti is a lightweight rock-solid BPMN 2.0 engine but still a long a way to go in matching the features supported by commercial implmentation of BPM products. seamless integration of LDAP, SSO, REST implementation, dehydration store management, administration console for instance management, identifying faulted instances and recovering them.
Just my two cents worth of thoughts about Activiti.

[bsethuramalinga]

Thanks for the suggestion. I will try that. I have been an admin oracle fusionmw products and kind of big shift for me to make migration to open source software like Activiti. If possible, please upload the log4j.properties or log4j.xml to debug activiti-engine / activiti-explorer. Please pardon my ignorance.

Thanks.

[mmaker1234]

Hello,

I would suggest you to check your Activiti Engine logging. Look in the User Guide on how to tune the logging. It could be tricky as it depends on your engine environment therefore it couldn't be described in a forum post especially with that minimum info from your side.

Another approach is to debug your code:
- break on the point where you call Activiti to start the process;
- configure your development environment to stop on any Throwable;
- execute the Activiti call.
This way you can catch the exception thrown by Activiti during the process start.

[mmaker1234]

I directed you to the Activiti User Guide because it explains that Activiti uses SLF4j (and not log4j) and further refers to SLF4j site for (quite good) explanations on how to tune Activiti to log in different environments.

[frederikherema1]

ALter the log-level of the classes you're interested in (eg. to finest/debug, depending on the log-impl). If you're not sure what you're interested in, set the level for "org.activiti" to debug/finest to get the full log and filter out what classes you're interested in an which not.