tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29671] - Context don't start with multiple HTTP 1.1 connectors
Date Wed, 11 Aug 2004 16:22:32 GMT
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

mbass@alphaconinc.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From mbass@alphaconinc.com  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
mbass@alphaconinc.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message