Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.6
-
Fix Version/s: JRuby 1.6.1
-
Component/s: None
-
Labels:None
-
Environment:HideJava 1.6.0_22 (64-bit) on both Mac OS X 10.6.6 (Snow Leopard) and Ubuntu 10.10 (Maverick Meerkat)
jruby 1.6.0 (ruby 1.8.7 patchlevel 330) (2011-03-15 f3b6154) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_22) [darwin-x86_64-java]
jruby 1.6.0 (ruby 1.8.7 patchlevel 330) (2011-03-15 f3b6154) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_22) [linux-amd64-java]ShowJava 1.6.0_22 (64-bit) on both Mac OS X 10.6.6 (Snow Leopard) and Ubuntu 10.10 (Maverick Meerkat) jruby 1.6.0 (ruby 1.8.7 patchlevel 330) (2011-03-15 f3b6154) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_22) [darwin-x86_64-java] jruby 1.6.0 (ruby 1.8.7 patchlevel 330) (2011-03-15 f3b6154) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_22) [linux-amd64-java]
-
Testcase included:yes
-
Number of attachments :
Description
Socket#accept_nonblock doesn't work at all in JRuby 1.6.0. It simply raises Errno::EAGAIN whether or not there is a new connection.
I've attached a test case that passes under both MRI 1.8.7 and JRuby 1.5.6, but fails under JRuby 1.6.0.
