Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.12.0.GA
Affects Version/s: 7.11.0.GA
Component/s: Kie-Server
Labels:
None
Environment:

Hide

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-standalone

Show
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-standalone

Blocked:
False
Ready:
False
Affects Build:
CR1
Fix Build:
ER1
Release Note Text:
Undefined
Target Release:

7.12.0.GA
Git Pull Request:
https://github.com/kiegroup/jbpm/pull/1944
Steps to Reproduce:

Hide

Start H2 server on TCP
Install 2 EAP instances with Kie servers pointing to the shared H2 instance, configure the instances according to the 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

Start reoccurring job on one instance using "org.kie.server.services.jbpm.cluster.ReoccurringLongPrintOutCommand"
Terminate the instance running the reoccurring job.
=>
The job is not retriggered in the second Kie server instance (it is expected to be retriggered).

Show
Start H2 server on TCP Install 2 EAP instances with Kie servers pointing to the shared H2 instance, configure the instances according to the 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 Start reoccurring job on one instance using "org.kie.server.services.jbpm.cluster.ReoccurringLongPrintOutCommand" Terminate the instance running the reoccurring job. => The job is not retriggered in the second Kie server instance (it is expected to be retriggered).

Sprint:
2021 Week 19-21 (from May 10), 2021 Week 22-24 (from May 31)

SFDC Cases Counter:
SFDC Cases Links:

Description

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]

Attachments

Issue Links

is cloned by

JBPM-9752 Graceful shutdown leave hanging jobs with the state of a RUNNING causing the job to stale

Resolved

Activity

People

Assignee:: Enrique González Martínez (Inactive)

Reporter:: Karel Suta

Tester:: Karel Suta

QA Contact:: Karel Suta

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2021/05/18 2:39 PM

Updated:: 2024/02/12 9:20 AM

Resolved:: 2021/06/03 12:47 PM