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-08 00:42 ------- (In reply to comment #17) > I don't think anyone is looking to place blame here. I don't care what was > originally in the Tomcat code and what is there now or why it was changed. > This simply comes down to a legitimate issue that needs to be resolved. It's > not even a minor issue frankly, it's a pretty substantial one, regardless of > the fact that it apparently hasn't caused huge problems for everyone. I'm not even sure if I've been bitten by this either, but I have seen on the list numerous people speaking of running out of Tomcat threads and setting their connections to the max. If this issue were causing problems they might be having it and not even realize it. > If the spec needs to be fixed, no problem, contact who needs to be contacted > and let them know. But that DOES NOT mean you serialize and wait for them to > do their thing. There is a solution here that, to my understanding, isn't > contrary to the spec as it exists today anyway, so not following through with > it is kind of silly. I'm sure any number of people would be willing to > submit > a patch for this if it's an issue of not having time, but to be arguing about > whether it should be fixed or not doesn't seem to be reasonable on this one. I agree....synchronizing these calls isn't going to be contrary to the spec in no way at all. -- 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]
