Issues with BasicSocket#close_read
----------------------------------
Key: JRUBY-2843
URL: http://jira.codehaus.org/browse/JRUBY-2843
Project: JRuby
Issue Type: Bug
Components: Rails WAR Deployment
Environment: Mac OS 10.5, JDK 5
Reporter: Federico Builes
BasicSocket#close_read is not being properly managed in JRuby:
{noformat}
$ jruby -rsocket -e "s = TCPServer.new(1234); s.close_read; s.close_read rescue
nil; p s.closed?"
#=> true
{noformat}
This of course should return false since closing one end of the socket is not
the same as closing the socket. In this case the socket will remain opened so
binding another socket to that same port will raise EADDRINUSE.
This is related to the specs found in
1.8/library/socket/basicsocket/close_read_spec.rb
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
