Bug 724368 (BRMS-314)

Summary: [JBRULES-2346] insert: ConcurrentModificationException on iterate of ObjectTypeConfigurationRegistry#typeConfMap.
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Toshiya Kobayashi <tkobayas>
Component: BRE (Expert, Fusion)Assignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0.1   
Target Milestone: ---   
Target Release: 5.1.0 GA, 5.1.0.ER1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-314
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-10 00:26:31 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:

Description Toshiya Kobayashi 2010-05-03 16:07:42 UTC 
Affects: Release Notes
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/580453
securitylevel_name: Public

Platform JIRA for [JBRULES-2346] insert: ConcurrentModificationException on iterate of ObjectTypeConfigurationRegistry#typeConfMap.
Comment 1 Toshiya Kobayashi 2010-06-17 11:22:21 UTC 
Link: Added: This issue incorporates JBRULES-2346
Comment 2 Tihomir Surdilovic 2010-09-07 19:08:13 UTC 
Resolved. Fix in 5.1
Comment 3 Dana Mison 2010-10-27 02:54:43 UTC 
Release Notes Text: Added: test
Comment 4 Dana Mison 2010-10-27 03:13:02 UTC 
Release Notes Text: Removed: test
Comment 5 Dana Mison 2010-11-19 05:10:57 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: Darrin
Comment 6 Petr Široký 2010-11-25 16:43:01 UTC 
Verified fixed in BRMS 5.1.0 ER4.
Comment 7 David Le Sage 2010-12-10 00:26:22 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Writer: Removed: Darrin Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/JBRULES-2346

ConcurrentModificationExceptions would occasionally occur in multi-thread environments.  This was due to a locking problem with the HashMap code.  To rectify this problem, HashMap has been replaced with ConcurrentHashMap.  As a result, users will no longer encounter these exceptions.