>> OTOH, I don't think this should be the case, and I think we should >> stop/start the server socket in that particular case, as was done in the >> old HTTP connector:
One thing to consider here - the CHUID case, where you bind on 80 and then change the user id. You can stop the server socket, but you can't open it - the only solution would be to restart tomcat. Is there any other way to 'recover' the server socket ? I personally consider this an OS bug - if a server socket becomes invalid. I suspect Apache 2.0 would also be affected by this - do we know anything about their workarounds ? Costin -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
