-
Bug
-
Resolution: Done
-
Major
-
7.11.0.GA
-
None
-
EAP 7.3.6
2 Kie servers configured for failover clustering according to https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.10/html/installing_and_configuring_red_hat_process_automation_manager/clustering-ps-con_clustering-runtime-standalone#clustering-kie-server-failover-proc_clustering-runtime-standaloneEAP 7.3.6 2 Kie servers configured for failover clustering according to https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.10/html/installing_and_configuring_red_hat_process_automation_manager/clustering-ps-con_clustering-runtime-standalone#clustering-kie-server-failover-proc_clustering-runtime-standalone
-
False
-
False
-
CR1
-
-
-
-
-
-
-
ER1
-
Undefined
-
-
-
2021 Week 19-21 (from May 10), 2021 Week 22-24 (from May 31)
Fail-over of a RUNNING job in kie-server executor doesn't work properly in 7.11.0 CR1.
When I run the reoccurring job provided as an example in Kie server (org.kie.server.services.jbpm.cluster.ReoccurringLongPrintOutCommand) and terminate the Kie server then only the original job is passed to the second Kie server, ignoring the currently running job (the one which should be actually reran):
16:20:15,161 INFO [org.kie.server.services.jbpm.cluster.ClusteredJobFailOverListener] (thread-12,ejb,fedora) Node left cluster Cluster Node [null-null], failing over and requeuing [1]
It works properly in 7.10.1, passing both original and currently running job:
16:15:40,663 INFO [org.kie.server.services.jbpm.cluster.ClusteredJobFailOverListener] (thread-10,ejb,fedora) Node left cluster Cluster Node [null-null], failing over and requeuing [1, 3]
- is cloned by
-
JBPM-9752 Graceful shutdown leave hanging jobs with the state of a RUNNING causing the job to stale
- Resolved