Bug 1148865
| Summary: | Cloning a repository via REST API doesn't finish on BPM cluster | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||
| Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> | ||||
| Status: | CLOSED EOL | QA Contact: | Radovan Synek <rsynek> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.1.0 | CC: | kverlaen, porcelli | ||||
| Target Milestone: | ER2 | Keywords: | TestBlocker | ||||
| Target Release: | 6.1.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 20:06:13 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: | |||||||
| Attachments: |
|
||||||
|
Description
Radovan Synek
2014-10-02 14:45:34 UTC
Created attachment 943406 [details]
maven based reproducer
Radek, after some "ping pong" for assignee of this task I tried to reproduce it and it looks like the cause of it is the size of repository you try to clone. It will eventually clone it and the job status will be SUCCESS but it does take some time. when you try to clone smaller one e.g. https://github.com/guvnorngtestuser1/guvnorng-playground.git then it does finish much faster. Though while doing these tests I ran into issues with social events causing lots of synchronizations between cluster members this assigned to Eder/Alex. Additional attempt ended up in "ACCEPTED" state while cloning the repository. Likely the issue does not occur any time. Radek, that's very valuable information that opened my eyes, since we use jbpm executor for async jobs it's distributed across all cluster members and that's why sometimes you get the proper status and sometimes not as the job statues is kept in memory only. I'll work on this to provide reliable approach. @Alex, I take this one and will create new one for the social issues in cluster. fixed by ensuring that given instance of the server will process a job that defines the owner property for it. That applies to all Guvnor REST operations and deployment operation to ensure same server instance will process it to be able to properly report status of the job. droolsjbpm-knowledge master: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/48ef49e5b2cd39f0e432ee2973d7d1aa9af8f06b 6.2.x: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/2b950579f0ae94827f945e28710ddd5449ed5b14 jbpm master: https://github.com/droolsjbpm/jbpm/commit/daa6e0e6a5ac3fcce25204fb5e1f7d86aeea8282 6.2.x: https://github.com/droolsjbpm/jbpm/commit/4871b0e808b6856fda72962c31080493097b863c droolsjbpm-integration master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/acf5938de514a871b46faaf7ad4b8d9e7fb5ab5a 6.2.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/6c64532a1c4c3151e926d600acdb6f41db0451e8 guvnor master: https://github.com/droolsjbpm/guvnor/commit/1d17adf0dfd370723ef25e22f965bc062378ddc7 6.2.x: https://github.com/droolsjbpm/guvnor/commit/b90174eefec04fbc6f74a85a3d774663d397deeb Verified with BPMS-6.1.0.ER2 |