| Summary: | [GSS] (6.2.z) Opening a repository takes a long time in BRMS 6.2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Oscar Molina <omolinab> | ||||
| Component: | Business Central | Assignee: | manstis | ||||
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.3.0 | CC: | kverlaen, lpetrovi, manstis | ||||
| Target Milestone: | CR1 | ||||||
| Target Release: | 6.2.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1296588 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-03-27 19:37:28 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: | |||||
| Bug Depends On: | 1296588 | ||||||
| Bug Blocks: | 1288021, 1288023 | ||||||
| Attachments: |
|
||||||
Created attachment 1112420 [details]
It contains the repositories to clone: ClaimsCycle and Authorization
|
Created attachment 1112419 [details] Thread dumps collected by the customer for comparing between BRMS 6.1 and BRMS 6.2 Description of problem: We have a customer who has installed a BRMS 6.2 and migrated their rules from BRMS 6.1. They have two repositories (ClaimsCycle and Authorization). ClaimsCycle repo has around 1200 rules and Authorization repo has 10 rules. When they try to switch "Authorization" repo to "ClaimsCycle" repo from business central it is taking more than 20 mins to open the ClaimsCycle repo in BRMS 6.2 while in BRMS 6.1 it was taking 1 to 2 mins. We have followed the same steps as customer and we have reproduced the same issue. Version-Release number of selected component (if applicable): BRMS 6.2.0 - EAP 6.4.5 How reproducible: We have attached the files useful for the test and analysis: --> Thread Dumps 6.1-6.2.zip - It contains the thread dumps collected by the customer for comparing between BRMS 6.1 and BRMS 6.2. 1. Thread Dumps_6.1 --> thread dump for BRMS 6.1 2. Thread Dump__6.2_1st Set --> 1st set of thread dump of BRMS 6.2 3. Thread Dump__6.2_2nd Set --> 2nd set of thread dump of BRMS 6.2 --> niogit.rar - It contains the repositories to clone: ClaimsCycle and Authorization --> repository.zip - It contains the JARs files used by the ClaimsCycle repository Steps to Reproduce: 1. Install EAP 6.4.5 2. Install BRMS 6.2.0 3. Access to business central and login 4. Go to Authoring -> Administration 5. Repositories -> Clone repository Repository Name: ClaimCycle Organizational Unit: example Git URL: file://<path_to_ClaimsCycle.git_in_.niogit> 6. Repositories -> Clone repository Repository Name: Authorization Organizational Unit: example Git URL: file://<path_to_Authorization.git_in_.niogit> 7. Go to Authoring -> Artifact repository Upload the following files from repository.rar: brms_mednext_drop_down-1.jar data-package-1.0.jar ojdbc-14.jar ons-1.0.jar resource-3.1.2.jar transaction-3.0.jar 8. Go to Authoring -> Project Authoring 9. Authorization repository is selected in the Project Explorer 10. Switch to ClaimCyle repository in the Project Explorer 11. Go to com/daman/brms which contains all the rules (around 1200) -> it takes a lot of time in BRMS 6.2 Actual results: When we switch "Authorization" repo to "ClaimsCycle" repo from business central it is taking more than 20 mins to open the ClaimsCycle repo in BRMS 6.2. Expected results: It should be opened from 1 to 2 mins aprox as in BRMS 6.1.