Bug 1090147
| Summary: | Thread locking problem on server that is going to shutdown | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ondrej Chaloupka <ochaloup> | ||||||
| Component: | EJB | Assignee: | David M. Lloyd <david.lloyd> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondrej Chaloupka <ochaloup> | ||||||
| Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 6.3.0 | CC: | hhovsepy, jcacek, jkudrnac, kkhan, pjelinek, rhatlapa, rsvoboda, smumford | ||||||
| Target Milestone: | ER3 | ||||||||
| Target Release: | EAP 6.3.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-06-28 15:29:54 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1051640 | ||||||||
| Attachments: |
|
||||||||
|
Description
Ondrej Chaloupka
2014-04-22 17:37:08 UTC
Created attachment 888606 [details]
server.stacktrace.dump
Definitely a bug. Needs upstream too though. The issue was as well hit for EAP integration testsuite running against databases in our test lab (e.g. postgresql, oracle etc.). It seems that the undeploying of the driver could somelike play some role in this. I need to point out that I'm now running my testing with the 'hot fix' and I have to say that it seems that it causes a warning being written to log (time to time). The server is correctly stopped and then it could be started without problem but the log contains a bit unlovely message. 06:29:42,923 WARN [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000004: Failure during stop of service jboss.deployment.unit."dsdriver.jar".moduleDeploymentRuntimeInformation: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859) [rt.jar:1.7.0_51] at java.util.ArrayList$Itr.next(ArrayList.java:831) [rt.jar:1.7.0_51] at org.jboss.as.ejb3.deployment.DeploymentRepository.remove(DeploymentRepository.java:111) at org.jboss.as.ejb3.deployment.ModuleDeployment.stop(ModuleDeployment.java:74) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2088) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2049) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] The line numbers don't seem to match up with my local copy, and I don't see anyplace where this should even be possible? Ah if you're testing your "remove synch" patch - that is definitely not a viable solution, though it was helpful in diagnosing the problem. You should use the attached fix instead. OK, I see. I will take it from your pull request. Sorry for the buzz. Verified on 6.3.0.ER3. The hang up troubles on shutdown disappeared and the change is part of the code (checked the decompiled jar jboss-as-ejb3-7.4.0.Final-redhat-11) Marking for exclusion from 6.3.0 Beta release notes as both 'affects' and 'fix' versions are listed as 6.3.0, suggesting this was not a customer-facing issue. |