DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29943>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29943 TokenProcessor generates double tokens on fast processors [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2004-07-07 21:14 ------- Committed a modified version of your fix, incorporating David's suggestion to simply check for duplicate values. It does add another synchronization point (I have no idea why generateToken() was public in the first place; it should have been protected), but my understanding is that the JVM will detect that saveToken() will have taken out the lock already, and not cost any time. As for the IllegalStateException, I'm drawing a blank on why that was ever there in the first place ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
