Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-9212

Stabilize GlobalQuartzDBTimerServiceTest - testInterediateTimerWithGlobalTestService

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 7.39.0.Final
    • KieServer
    • None
    • NEW
    • NEW

      This is a flaky test, due to use of sleeps, instead of countdown latch. When the sleeping time is not enough for all the three timers to be fired, this error is happening:

      Error Message

      expected null, but was:<WorkflowProcessInstance1 [processId=IntermediateCatchEvent,state=1]>

      Stacktrace

      java.lang.AssertionError: expected null, but was:<WorkflowProcessInstance1 [processId=IntermediateCatchEvent,state=1]> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotNull(Assert.java:755) at org.junit.Assert.assertNull(Assert.java:737) at org.junit.Assert.assertNull(Assert.java:747) at org.jbpm.test.functional.timer.GlobalTimerServiceBaseTest.testInterediateTimerWithGlobalTestService(GlobalTimerServiceBaseTest.java:165) 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.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748)

       

      Standard Output

      2020-06-30 02:59:36,649 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa]; persistence-unit names must be unique 2020-06-30 02:59:36,651 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa]; persistence-unit names must be unique 2020-06-30 02:59:36,651 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.services.task]; persistence-unit names must be unique 2020-06-30 02:59:36,651 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.patient.example]; persistence-unit names must be unique 2020-06-30 02:59:36,652 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa]; persistence-unit names must be unique 2020-06-30 02:59:36,653 [main] WARN HHH015018: Encountered multiple persistence-unit stanzas defining same name [org.jbpm.persistence.jpa.local]; persistence-unit names must be unique 2020-06-30 02:59:37,279 [main] WARN HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered 2020-06-30 02:59:37,279 [main] WARN HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered 2020-06-30 02:59:37,397 [Time-limited test] INFO PerProcessInstanceRuntimeManager is created for default-per-pinstance 2020-06-30 02:59:37,412 [Time-limited test] INFO Using default implementation for ThreadExecutor 2020-06-30 02:59:37,415 [Time-limited test] INFO Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2020-06-30 02:59:37,415 [Time-limited test] INFO Quartz Scheduler v.2.3.2 created. 2020-06-30 02:59:37,415 [Time-limited test] INFO Using db table-based data access locking (synchronization). 2020-06-30 02:59:37,415 [Time-limited test] INFO JobStoreCMT initialized. 2020-06-30 02:59:37,415 [Time-limited test] INFO Scheduler meta-data: Quartz Scheduler (v2.3.2) 'TestScheduler' with instanceId 'instance_one' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 15 threads. Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreCMT' - which supports persistence. and is not clustered. 2020-06-30 02:59:37,415 [Time-limited test] INFO Quartz scheduler 'TestScheduler' initialized from specified file: 'quartz-db.properties' in the class resource path. 2020-06-30 02:59:37,415 [Time-limited test] INFO Quartz scheduler version: 2.3.2 2020-06-30 02:59:39,418 [Thread-170] INFO Freed 0 triggers from 'acquired' / 'blocked' state. 2020-06-30 02:59:39,419 [Thread-170] INFO Recovering 0 jobs that were in-progress at the time of the last shut-down. 2020-06-30 02:59:39,419 [Thread-170] INFO Recovery complete. 2020-06-30 02:59:39,419 [Thread-170] INFO Removed 0 'complete' triggers. 2020-06-30 02:59:39,419 [Thread-170] INFO Removed 0 stale fired job entries. 2020-06-30 02:59:39,419 [Thread-170] INFO Scheduler TestScheduler_$instance_one started. Timer triggered Timer triggered 2020-06-30 02:59:42,973 [main] INFO Scheduler TestScheduler$instance_one shutting down. 2020-06-30 02:59:42,973 [main] INFO Scheduler TestScheduler$instance_one paused. 2020-06-30 02:59:43,426 [main] INFO Scheduler TestScheduler$_instance_one shutdown complete.

       

       

            gmunozfe@redhat.com Gonzalo Muñoz Fernández
            gmunozfe@redhat.com Gonzalo Muñoz Fernández
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: