Bug 1055632 - Incremental build may fail with ConcurrentModificationException
Summary: Incremental build may fail with ConcurrentModificationException
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER1
: 6.0.1
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-20 16:06 UTC by Jiri Locker
Modified: 2014-08-06 19:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:56:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
server.log with exception stack trace (4.82 KB, text/plain)
2014-01-20 16:06 UTC, Jiri Locker 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1045095 0 medium CLOSED Incremental build fails intermittently when creating a new project 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1052131 0 medium CLOSED NPE in server log when creating new rule 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1055941 0 low CLOSED No facts available after creating new guided rule, NPE in server log 2021-02-22 00:41:40 UTC

Internal Links: 1045095 1052131 1055941

Description Jiri Locker 2014-01-20 16:06:29 UTC 
Created attachment 852793 [details]
server.log with exception stack trace

Description of problem:
When creating new resources, incremental build is requested multiple times. It appears that requests are handled by different threads with no synchronization mechanism being implemented. These threads may access a shared resource concurrently causing java.util.ConcurrentModificationException which is the logged in server log.

Version-Release number of selected component (if applicable):
6.0.0.CR1

How reproducible:
Probably race condition.

Steps to Reproduce:
-

Actual results:
Incremental build may fail with java.util.ConcurrentModificationException. The exception is logged in server log.

Expected results:
Synchronization mechanism for processing incremental builds needed to prevent CME.

Additional info:
Comment 3 Jiri Locker 2014-03-07 09:09:03 UTC 
This is difficult to »verify« but:

- The fix looks good.
- The test looks reasonable, it fails before the fix and passes with the fix.
- I haven't seen the CME in server log since 6.0.1.ER1
Note You need to log in before you can comment on or make changes to this bug.