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=37356>. 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=37356 ------- Additional Comments From [EMAIL PROTECTED] 2006-03-10 08:54 ------- > > Generally this is not enough to have thread-safe code. For instance this kind > of > code is not thread-safe: > this.x--; > if (this.x == 0) ... > In this case AtomicInteger.decrementAndGet can be used. Of course, but as far as I could tell, in the tomcat session-management there is a sessionCount-- for every sessionCount++, so in the end there should be a total sessionCount of 0. Maybe one of the checks for sessionCount==0 does not always immediately give the 'correct' result - but in the long run it has always to return to zero. > > > > > So the trigger has to be either the 64bit CPU / Java or Tomcat and mod_jk, > > or > > something in my configuration (the application is the same .war file) > > Threading problems (ie lack of synchronization) are more visible on multi-CPU > or > multi-core configurations. > I'll have to check if all machines we see this on are multi-core... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
