topic Deadlock in Junit test in Alfresco Archive

Deadlock in Junit test

pika822 — Fri, 21 Nov 2014 10:39:41 GMT

Hello,Excus eme if this topic is a duplication, it's the third time I try to create it.I have a random deadlock during a Junit test suite. The tests are executed sequentially. The deadlock happens only for a specific use case test. According to my other traces, the deadlock appears just before an as

Re: Deadlock in Junit test

trademak — Fri, 21 Nov 2014 15:42:54 GMT

Are you using threading in this unit test? H2 is not a good database to test multithreaded behavior in the Engine. You would need to test that in a "true" database.

Best regards,

Re: Deadlock in Junit test

pika822 — Fri, 21 Nov 2014 16:49:47 GMT

Thanks for your answer.
I don't think so. The unit test (which generates the error) has only one process instance in execution for this test. There are no parallel execution in the process definition, just an asynchronous service task. And the unit tests executions are sequential.
However, this error only appears when I execute all the tests of my Junit Class. It never appears when I launch just the unit test.

Re: Deadlock in Junit test

pika822 — Mon, 24 Nov 2014 11:06:24 GMT

I didn't check on a real database.
However, my process is designed to use JPA variables, and in my unit test, I didn't persist my variable. So I fixed that problem and it resolved the deadlock problem too.

Re: Deadlock in Junit test

jbarrez — Fri, 05 Dec 2014 14:08:23 GMT

Ok, very odd. But the main thing is your problem is gone 🙂