-
Bug
-
Resolution: Done
-
Minor
-
7.35.0.Final
-
None
-
NEW
-
NEW
-
Jenkins is reporting a test failure:
org.jbpm.test.functional.timer.ConcurrentGlobalTimerServiceTest.testSessionPerProcessInstance
Error Message
Failure, did not finish in time most likely hanging
Stacktrace
java.lang.AssertionError: Failure, did not finish in time most likely hanging at org.junit.Assert.fail(Assert.java:88) at org.jbpm.test.functional.timer.ConcurrentGlobalTimerServiceTest.testSessionPerProcessInstance(ConcurrentGlobalTimerServiceTest.java:152) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Standard Output
2020-03-25 14:46:00,789 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa]; persistence-unit names must be unique 2020-03-25 14:46:00,790 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa]; persistence-unit names must be unique 2020-03-25 14:46:00,790 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.services.task]; persistence-unit names must be unique 2020-03-25 14:46:00,790 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.patient.example]; persistence-unit names must be unique 2020-03-25 14:46:00,791 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa]; persistence-unit names must be unique 2020-03-25 14:46:00,791 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa.local]; persistence-unit names must be unique 2020-03-25 14:46:01,022 [main] WARN HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered 2020-03-25 14:46:01,022 [main] WARN HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered 2020-03-25 14:46:01,061 [main] INFO PerProcessInstanceRuntimeManager is created for default-per-pinstance 2020-03-25 14:46:01,066 [main] WARN ProcessInstanceIdContext or CorrelationKeyContext shall be used when interacting with PerProcessInstance runtime manager