DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9935>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9935 Odd port 32769 left in BOUND state ------- Additional Comments From [EMAIL PROTECTED] 2002-07-08 23:31 ------- Oddly enough, on Solaris I was able to reproduce the problem when a more than a socket gets bound... Like ServerSocket s1=new ServerSocket(1233); ServerSocket s2=new ServerSocket(1234); It appears to be a bug in the VM, but I'm not quite confident on that... It still looks odd (it happens once every N time, while with tomcat it happens ALL the times). As I posted on Tomcat-DEV, trussing the VM, it shows that actually the sucker does create the two sockets, and does make the odd connections, plus, leaves one of the sockets in "bound" state... But ATM not much time to debug the VM... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
