PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3374 *** shadow/3374 Sun Sep 2 09:46:33 2001 --- shadow/3374.tmp.13193 Sun Sep 2 13:13:02 2001 *************** *** 2,9 **** | ArrayIndexOutOfBoundsException | +----------------------------------------------------------------------------+ | Bug #: 3374 Product: ORO | ! | Status: NEW Version: 2.0.4 | ! | Resolution: Platform: Sun | | Severity: Blocker OS/Version: Solaris | | Priority: Other Component: Main | +----------------------------------------------------------------------------+ --- 2,9 ---- | ArrayIndexOutOfBoundsException | +----------------------------------------------------------------------------+ | Bug #: 3374 Product: ORO | ! | Status: RESOLVED Version: 2.0.4 | ! | Resolution: INVALID Platform: Sun | | Severity: Blocker OS/Version: Solaris | | Priority: Other Component: Main | +----------------------------------------------------------------------------+ *************** *** 34,37 **** changed the code such that the patternMatcher is no longer static. So, is the method thread safe? It doesn't appear to be. ! Tom --- 34,45 ---- changed the code such that the patternMatcher is no longer static. So, is the method thread safe? It doesn't appear to be. ! Tom ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-09-02 13:13 ------- ! This is not a bug. Patterns must be compiled with READ_ONLY_MASK if they ! are to be shared between threads. Furthermore, one Perl5Matcher instance ! should be used per thread. This used to be made clear in the OROMatcher ! user's guide. If you don't want to optimize performance by avoiding the ! overhead of synchronization, use Perl5Util instead. !
