[TAPESTRY-1234] ResourceMatcherImpl not thread safe on multi-CPU system

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.1.1
• Fix Version/s: 4.1.2
• Component/s: Framework, tapestry-core
• Assignee: Jesse Kuhnert
• Reporter: Greg Woolsey
• Created: 20/Jan/07 18:40
• Updated: 22/Jan/07 00:37
• Resolved: 22/Jan/07 00:37

Description

Load testing on a multi-CPU system uncovered another thread safety issue. I'm not sure why, because I'm unclear on the call flow, but the RegexpMatcher instance held by ResourceMatcherImpl can be called by two threads at once. This leads to predictable ArrayIndexOutOfBounds errors down in the ORO Perl5Matcher class, because that class has instance state that is being accessed by both threads, similar to the SimpleDateFormat issue in TAPESTRY-1229.

I turned it into a ThreadLocal, which worked, but I think that loses some of the pattern caching performance benefits. Not sure what the best solution is, but a ThreadLocal is guaranteed to be safe.