Bug 1075073
| Summary: | AlreadyClosedException: "this IndexWriter is closed" error when shutting down Business-Central cluster | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||||
| Component: | Business Central | Assignee: | Alexandre Porcelli <porcelli> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.1 | CC: | kverlaen | ||||||
| Target Milestone: | ER1 | ||||||||
| Target Release: | 6.0.2 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 19:50:51 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: |
|
||||||||
Created attachment 873103 [details]
server log - node two
After a while trying to reproduce, I manage to understand what the issue is... and it's not related to clustering, it's related to repository indexing... specially if you clone a big enought repo with several branches (to be able to reproduce issue I used our kie-wb-distributions github repo). Fix on master and product branch of uberfire repository: (0.3.x) http://github.com/uberfire/uberfire/commit/aeb5849ec (master) http://github.com/uberfire/uberfire/commit/3ced7c57a Verified with BPMS-6.0.2.ER2. |
Created attachment 873102 [details] server log - node one The "org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed" raises for - as it seems - every asset in a repository when the Business-Central cluster is shutting down. Steps to Reproduce: 1. configure a Business-Central cluster with 2 EAP nodes 2. log in, clone some repository containing project with various assets 3. build & deploy the project 4. shut the cluster down 5. observe server logs.