Bug 1283953
| Summary: | Cluster node hangs while trying to show content created on a different node | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||||||
| Component: | Business Central | Assignee: | Alexandre Porcelli <porcelli> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Radovan Synek <rsynek> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | 6.2.0 | CC: | kverlaen, manstis, porcelli, rrajasek | ||||||||
| Target Milestone: | CR2 | Keywords: | Regression | ||||||||
| Target Release: | 6.2.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2020-03-27 19:06:54 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1271898 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 1097119 [details]
screenshot node one
Created attachment 1097120 [details]
screenshot node two
Fixes: https://github.com/uberfire/uberfire/commit/4dbd922dc942b0801d0f1bae0ab19fbae009a595 https://github.com/droolsjbpm/guvnor/commit/6e407f21c3d6db0ea1793af4271d3b3dc01ea121 Master: https://github.com/uberfire/uberfire/commit/0d9af94fd979a9eaeadc7a9c11e036d83acafa79 https://github.com/droolsjbpm/guvnor/commit/38480b5d745d02bf0f16820bc88a9c4265427e15 Verified with BPMS-6.2.0.CR2 |
Created attachment 1097116 [details] logs and configuration files Description of problem: Having a BPM cluster with 2 nodes running in EAP domain, the following use case fails: 1. start a cluster 2. operate on the node#1: a. create an organization unit b. create a new repository c. create a project d. create a DRL file in the project, write there a simple rule e. save the DRL file 3. operate on the node#2 a. open the DRL created in step 2.d from this point, the UI on node#2 hangs; refresh does not help. Additional info: attaching jstack report of both nodes as well as server logs and configuration files.