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 33474] - tcpListenPort="0" won't get actual local port for cluster membership
Date Thu, 10 Feb 2005 15:43:44 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=33474>.
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=33474





------- Additional Comments From cstach-asf@ldsys.net  2005-02-10 16:43 -------
I have to disagree with marking this as invalid.  It _is_ marked as an 
enhancement and it would be much easier to tell when or if it is implemented 
with this for tracking.

I couldn't find any other dependencies on the listener port.  The only other 
issue is making the bind happen in the calling thread inside of start() and not 
in the listener's thread.  I don't know why you would continue processing the 
cluster (or even starting another thread in this case) if you can't get a 
required resource, even if it may save a little time.  I didn't see anything 
required for the bind that could block for any long period of time, so putting 
it in the calling thread wouldn't do any harm.

If there are any "dependencies" outside of that, that's non-OO and bad news.

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message