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=36541>. 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=36541 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-09 15:12 ------- (In reply to comment #67) > (In reply to comment #66) > > http://java.sun.com/j2se/javadoc/writingapispecs/index.html#top-level > > That reference is invalid in the context of this bug report. I read it to be > a > hyperthetical example of what to put inside javadoc information. > > Nothing concrete to under pin all Java programming design. I think what leon is trying to say is that 'this is what should be done'. So either - the documentation for HTTPsession has a problem, that it is missing the information regarding it not being thread safe - or the implementation in TC is wrong. According to what I have read here, it has been decided that TC says that HTTPsession is NOT threadsafe, meaning that all developers who use HTTPsession will - should they call 'put' - need to ensure that they sync the session - otherwise nasty things can happen. This means that the documentation should definitely be changed to warn developers, and that all 3rd party projects fix their code so that it does not crash/ hang tomcat 5.0 . (I haven't had a proper look to check if the synced puts in 5.5 are enough to stop the loops)... IMHO - Anyone who doesn't care whether or not the data is consistent - really doesn't need the data, and shouldn't bother calling the routine. -- 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]
