Bug 983324
| Summary: | Seeing ConcurrentModificationException in EJBClientContext on start up. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | dstephan |
| Component: | EJB | Assignee: | Jaikiran Pai <jpai> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | bmaxwell, dimitris, dstephan, jmartisk, jpai, myarboro, smumford |
| Target Milestone: | ER7 | ||
| Target Release: | EAP 6.1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
This bugzilla addresses an issue in the EJB client library, where registering an EJBReceiver to a EJBClientContext could sometimes fail with java.util.ConcurrentModificationException because of an incorrect handling of a datastructure while dealing with multiple threads.
After this fix in the EJB client library, users won't be seeing this exception while registering EJBReceiver(s) to an EJBClientContext.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-16 20:24:13 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: | |||
It's already fixed in the version that's integrated for 6.1.1. Fixed in EJB client 1.0.22.Final, EAP 6.1.1.ER7 contains 1.0.23.Final. Closing. |
Description of problem: Seeing this Stacktrace: Caused by: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) [rt.jar:1.7.0_21] at java.util.HashMap$KeyIterator.next(HashMap.java:928) [rt.jar:1.7.0_21] at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:390) at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:327) this looks to be fixed in 2.0.0.Beta here: https://github.com/jbossas/jboss-ejb-client/commit/8a34304c78f7008a79a743f4f750ffec1c48ab91 Can this be included in EAP 6.1.x ?