Created attachment 997924 [details] server log node one Description of problem: Having a BPM cluster with two EAP 6.4 nodes in a domain, sometimes the second cluster node fails to deploy business central properly due to org.eclipse.jgit.api.errors.ConcurrentRefUpdateException: Could not lock HEAD. RefUpdate return code was: LOCK_FAILURE. Please take a look at attached server logs. In Majority of attempts the issue does not occur, it's likely a synchronization problem. The first node seems to be working and responsive, the second node is completely lost when the issue happens. Version-Release number of selected component (if applicable): 6.1.0.ER5 How reproducible: 10% - 20% Steps to Reproduce: 1. configure two EAP 6.4 nodes in domain mode together with helix and zookeeper 2. deploy business central 3. watch for errors in server logs
Created attachment 997925 [details] server log node two
Alex, unfortunately the issue shows itself with ER6 as well, attaching new server log excerpt.
Created attachment 999911 [details] server log excerpt ER6
What exactly setup this happens? I mean.. is this first startup (no existing repo)? Or is this happens during a restart of an existing setup (some repos already existis)?
Last time it happened after a failover simulation, so the repository should have been there. To be more specific, exception showed on node two, but node one was stopped and started again.
Additional improvements: (master) http://github.com/uberfire/uberfire/commit/f656d837f Here a change to remove a missing sync method: (master) http://github.com/droolsjbpm/kie-wb-common/commit/0ab922f2d
Requesting blocker flag for backport to 6.2.x
Pushed to product branches: (6.2.x) https://github.com/droolsjbpm/kie-wb-common/commit/0be965d088f0deee49f63cf0cd1391c32fe1efda (0.5.x) https://github.com/droolsjbpm/kie-wb-common/commit/0be965d088f0deee49f63cf0cd1391c32fe1efda
Maybe from a different place, but the "could not lock HEAD" error is still being thrown, take a look at the new log excerpt (CR1)
Created attachment 1007330 [details] server log excerpt CR1
New fixes: https://github.com/uberfire/uberfire/commit/f55557b526eec060023a859225776ba51d19a375 https://github.com/uberfire/uberfire-extensions/commit/83df5ebf35aaa2cafd2af65032e0bc4d683b523a
Verified with BPMS-6.2.0.ER5 that this problem no longer exists