nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

parallel exceptionhandling

al_lv

Hi,

I created tow processes with exception handling as it described in example files(with tansitions).
[attachment=1]siebel.png[/attachment]
[attachment=2]email.png[/attachment]

Now i want to run them parallel. So I created call activity with these processes and connected them with paralle gateway.
[attachment=0]EmailAndArchive.png[/attachment]

Is it a correct way to do somthing like this?

every last of these processes works fine.
But together in the process with call-Activities I get this Error in TOmcat:

Caused by: java.sql.SQLException: Transaction (Process ID 65) was deadlocked on {lock} resources with another process and has been chosen as the deadlock victim. Rerun the transaction.‍

Pleas help

I run Activiti 5.8 with MSSQL
May be the problem is because I use in User Task the same Class as in the serviceTask? So i implement tow interfaces: ActivityBehavior and TaskListener

Thanks

Alexej

siebel.png

email.png

EmailAndArchive.png

Find more posts tagged with

Comments

trademak

Hi,

The BPMN process definitions seem to be fine.
What kind of transaction handling are you using?
Is there something complex happening in the service tasks?

Best regards,

al_lv

What kind of transaction handling are you using?

I dont know. I didn't change anything by activiti.

Is there something complex happening in the service tasks?

actually not. I just call funtionality of our software. it archives document in CRM-siebel. this is my class:

<br>public class SiebelTask extends C4ServiceTask{<br> private static final Logger LOG = LoggerFactory.make();<br> private Expression partnerSystem;<br><br> public void execute(ActivityExecution execution) throws Exception {<br>&nbsp; PvmTransition transition = null;<br>&nbsp; Map<String, Object> variables = new HashMap<String, Object>();<br><br>&nbsp; String partnerSystemStr = (String) partnerSystem.getValue(execution);<br><br>&nbsp; if (execution.hasVariables()) {<br>&nbsp;&nbsp; try {<br>&nbsp;&nbsp;&nbsp; LOG.info("Starting siebel task. ThreadID: "<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + Thread.currentThread().getId());<br><br>&nbsp;&nbsp;&nbsp; variables = execution.getVariables();<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; byte[] startupByte = (byte[]) variables.get("startup");<br>&nbsp;&nbsp;&nbsp; String startupXml = new String(startupByte);<br><br>&nbsp;&nbsp;&nbsp; Startup startup = new JaxbStartup(startupXml);<br>&nbsp;&nbsp;&nbsp; ConnectorBusinessData data = loadDataXml(variables.get("data"));<br><br>&nbsp;&nbsp;&nbsp; SiebelStartup siebelStartup = new SiebelStartup(startup);<br><br>&nbsp;&nbsp;&nbsp; SiebelRunner sr = new SiebelRunner(siebelStartup,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; partnerSystemStr);<br><br>&nbsp;&nbsp;&nbsp; Properties props = new Properties();<br><br>&nbsp;&nbsp;&nbsp; CallbackProperties callbackProperties = new CallbackProperties();<br>&nbsp;&nbsp;&nbsp; callbackProperties.setProperties(props);<br><br>&nbsp;&nbsp;&nbsp; sr.execute(new BusinessServiceInvoker(data, callbackProperties<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .getProperties()));<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; transition = execution.getActivity().findOutgoingTransition(<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "siebel-no-exception");<br>&nbsp;&nbsp;&nbsp; LOG.info("Siebel task was succesfully completed. ThreadID: "<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + Thread.currentThread().getId());<br>&nbsp;&nbsp; } catch (Exception e) {<br><br>&nbsp;&nbsp;&nbsp; LOG.severe("ThreadID: " + Thread.currentThread().getId()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + "\nEs gibt ein Problem bei siebel task: " <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + e.getMessage());<br>&nbsp;&nbsp;&nbsp; transition = execution.getActivity().findOutgoingTransition(<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "siebel-exception");<br>&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; execution.take(transition);<br>&nbsp;&nbsp; <br>&nbsp; } else {<br>&nbsp;&nbsp; LOG.severe("Es gibt folgendes Problem: Die Processvariablen konnten nicht gesetzt werden.");<br>&nbsp; }<br><br> }<br>

CServiceTask implements AcitvityBehavior