Feature #1753
implement full locking/synchronization for all shared data in TRPL worker classes and other dependent Java code
Start date:
Due date:
% Done:
50%
Estimated time:
80.00 h
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Related issues
History
#1 Updated by Greg Shah over 13 years ago
- Target version set to Code Improvements
#2 Updated by Greg Shah over 9 years ago
- Estimated time changed from 40.00 to 80.00
- Target version changed from Code Improvements to TRPL 2.0
#3 Updated by Greg Shah about 1 year ago
- Related to Feature #3211: implement multi-threaded pattern engine and rework the ConversionDriver to leverage it added
#4 Updated by Greg Shah about 1 year ago
- Subject changed from implement full locking/synchronization for all shared data to implement full locking/synchronization for all shared data in TRPL worker classes and other dependent Java code
#5 Updated by Octavian Adrian Gavril about 1 year ago
- Status changed from New to WIP
- Assignee set to Octavian Adrian Gavril
#6 Updated by Octavian Adrian Gavril about 1 year ago
- % Done changed from 0 to 50
I've committed some changes with the locking/synchronization implementation of worker classes in 1752a/15891. I reviewed all worker classes, identifying shared data that requires multi-threading protection. I then checked the rulesets where these workers are used to determine which fields need thread-specific handling.