DO NOT REPLY [Bug 3877] - {n} and {n,m} not thread safe

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3877>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3877

{n} and {n,m} not thread safe

dougpardee@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|{0,n} matches 0 to n+1      |{n} and {n,m} not thread
                   |instead of 0 to n times.    |safe



------- Additional Comments From dougpardee@yahoo.com  2001-09-28 15:22 -------
Alas, the above suggestion won't help my problem.

The problem that I am having is occurring with a specification of "{9}". It is 
unrelated to the use of a lower limit of zero. The behavior is also not 
predictable, as it depends on timing of multiple threads (in this case, within 
a servlet). Most of the time it works fine, but every now and again...

One thread is wiping out the values of bracket, bracketMin, bracketOpt, etc., 
which are simultaneously being used by another thread. The source of the 
problem is that these are static variables, not member variables.