https://bz.apache.org/bugzilla/show_bug.cgi?id=62404
--- Comment #6 from Christopher Schultz <ch...@christopherschultz.net> --- In Mark's test, the second thread picked-up the changed value within 0.02sec. IMO, that's fast enough that issuing the property change itself might end up out-of-order and therefore the race isn't important. If this were a primitive long or double value, I might argue that synchronized access should be required because there a read/write race condition can cause a thread to read a *wrong* value (one that is neither the old-value nor the new-value). In this case, you just have (at least) two threads that (a) can perform tasks in any order and (b) aren't coordinated in any way that requires them to agree on what happened first. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
