Bug 994484
Summary: | Exception while saving bucket Bucket: FileNotFoundException at server shutdown | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jitka Kozana <jkudrnac> |
Component: | Clustering | Assignee: | Paul Ferraro <paul.ferraro> |
Status: | CLOSED EOL | QA Contact: | Michal Vinkler <mvinkler> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.1.1 | CC: | jkudrnac, lthon, myarboro, rhusar, rjanik |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | EAP 6.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-19 12:48:04 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: |
Description
Jitka Kozana
2013-08-07 11:23:37 UTC
Update after EAP 6.2.0. testing cycle: this issue was not seen during this testing cycle. If this issue was fixed, than please change the status of this BZ accordingly. Seen this happening with EAP 6.3.0.DR4: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbservlet-shutdown-repl-sync-modcluster-dualstack-ipv6/23/console-dev89/ Not sure if reopen is the right thing to do here. I've seen this again with EAP 6.3.0.ER4: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbservlet-jvmkill-repl-sync-modcluster-ipv6/56/console-vmg34/ Reopening. This does look like an environmental issue since it has been only seen on vmg-s. I have inspected the machines, the /tmp from where the test are run is quite small (4 GB) with stale files from non-hudson users which could have possibly conflicted and resulted in "No such file or directory". Could you reproduce this in clean environment such as perf*? Let me note, that even though the previously linked job is using JVM kill as failure type, the exception happens when the cluster is gracefully shut down. Still an issue (though very rare and it was suggested that it's possibly environmental, see comment 5), moving to 6.4 (for now, needs investigation). Lowering priority, given comment #6. Deferring clean shutdown issues to EAP7. |