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=29671>. 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=29671 Context don't start with multiple HTTP 1.1 connectors [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-08-11 16:22 ------- Resolution INVALID?!? How is this not a bug? I am having the same problem with 3 Connectors defined. Sometimes I get the error and when I do, one of my connectors is "unavailable". Sometimes I don't get the error and when I don't, all connectors are "available". So again I am left wondering as to how this is not a bug. Perhaps Tomcat should use a Hashtable or a synchronized HashMap to avoid the ConcurrentModificationException. Marion Bass [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
