Bug 988427
| Summary: | Exception thrown when stopping EAP - org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Jiri Svitak <jsvitak> | ||||
| Component: | Business Central | Assignee: | Alexandre Porcelli <porcelli> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Svitak <jsvitak> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.0 | CC: | mbaluch, rzhang | ||||
| Target Milestone: | ER3 | ||||||
| Target Release: | 6.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 20:18:36 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: |
|
||||||
Fixes on community project on master and 6.0.x branches https://github.com/droolsjbpm/kie-commons/commit/79b4561ef https://github.com/droolsjbpm/kie-commons/commit/9a547f07a Verified in BPMS 6 ER3. |
Created attachment 778292 [details] server.log I have used eap 6.1 and merged it with bpms deployable DR6 distribution. I started the server ./standalone.sh and when it started I stopped it with Ctrl+C and the following exception was thrown: (Thread-88) Exception in thread "Thread-88" org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed The rest of the exception is attached. This error is thrown just when stopping the server, so it's not something serious, but it should be fixed to not confuse customers. I think it's good idea to keep the server logs free of exceptions. Filing under BRMS as this error seem to be connected to underlying interaction with file system.