JRuby

JRuby 1.2.0 does not bind socket to 0.0.0.0 properly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: JRuby 1.2
  • Fix Version/s: None
  • Component/s: Core Classes/Modules, Intro
  • Labels:
    None
  • Environment:
    Ubuntu Linux 8.10. x86 Wired and wireless networking enabled.
  • Number of attachments :
    0

Description

When launching Webrick or Mongrel, the application is reported as starting on 0.0.0.0:3000 but when looking at the netstat -aon for the connection, the binding information is incorrect and the application cannot be contacted.

MRI Behavior:

Launch using ./script/server
$ netstat -aon | grep 3000

tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN off (0.00/0/0)

JRUBY 1.2.0 Behavior:

Launch using

{path to jruby}

/jruby ./script/server
$ netstat -aon | grep 3000

tcp6 0 0 :::3000 :::* LISTEN off (0.00/0/0)

Functionally, these two are not the same. When bound to 0.0.0.0:3000, the application can receive service requests on the specified port.

When bound to :::3000, the application doesn't see anything except requests to localhost.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. JRUBY-3241 Bug when binding to ipv4 port when same port is binded to ipv6 address

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Charles Oliver Nutter added a comment -

This could be easy for someone who knows how Java handles IP4/IP6 binding; it looks like we're trying to bind to IP6 by default. This may also have been fixed since the original report, or at least improved. Marking as Intro.

Show
Charles Oliver Nutter added a comment - This could be easy for someone who knows how Java handles IP4/IP6 binding; it looks like we're trying to bind to IP6 by default. This may also have been fixed since the original report, or at least improved. Marking as Intro.
Hide
Permalink
Hiro Asari added a comment -

As a reference point, here's what I get when I start a Rails app on Mac OS X.

surfboard:~$ netstat -an | grep 3000
tcp46      0      0  *.3000                 *.*                    LISTEN
tcp4       0      0  127.0.0.1.54579        127.0.0.1.3000         TIME_WAIT
tcp4       0      0  127.0.0.1.54582        127.0.0.1.3000         TIME_WAIT
tcp4       0      0  127.0.0.1.3000         127.0.0.1.54580        TIME_WAIT
tcp4       0      0  127.0.0.1.3000         127.0.0.1.54581        TIME_WAIT

A minimal server script (taken from http://ruby-doc.org/stdlib/libdoc/socket/rdoc/index.html)

require 'socket'
serv = TCPServer.new(2202)
begin
  sock = serv.accept_nonblock
rescue Errno::EAGAIN, Errno::ECONNABORTED, Errno::EPROTO, Errno::EINTR
  IO.select([serv])
  retry
end
# sock is an accepted socket.

also exhibits a similar behavior.

Show
Hiro Asari added a comment - As a reference point, here's what I get when I start a Rails app on Mac OS X. surfboard:~$ netstat -an | grep 3000 tcp46 0 0 *.3000 *.* LISTEN tcp4 0 0 127.0.0.1.54579 127.0.0.1.3000 TIME_WAIT tcp4 0 0 127.0.0.1.54582 127.0.0.1.3000 TIME_WAIT tcp4 0 0 127.0.0.1.3000 127.0.0.1.54580 TIME_WAIT tcp4 0 0 127.0.0.1.3000 127.0.0.1.54581 TIME_WAIT A minimal server script (taken from http://ruby-doc.org/stdlib/libdoc/socket/rdoc/index.html ) require 'socket' serv = TCPServer.new(2202) begin sock = serv.accept_nonblock rescue Errno::EAGAIN, Errno::ECONNABORTED, Errno::EPROTO, Errno::EINTR IO.select([serv]) retry end # sock is an accepted socket. also exhibits a similar behavior.
Hide
Permalink
Hiro Asari added a comment -

I should add that the previous comment was JRuby running the Rails app.

If MRI runs the app, here's what I get:

surfboard:~$ netstat -an | grep 3000
tcp4       0      0  *.3000                 *.*                    LISTEN
tcp46      0      0  *.3000                 *.*                    LISTEN
Show
Hiro Asari added a comment - I should add that the previous comment was JRuby running the Rails app. If MRI runs the app, here's what I get: surfboard:~$ netstat -an | grep 3000 tcp4 0 0 *.3000 *.* LISTEN tcp46 0 0 *.3000 *.* LISTEN
Hide
Permalink
Joseph LaFata added a comment -

Java tries to use IPv6 if available. A problem can occur if your network doesn't support IPv6. The problem is described more in depth here: http://activemq.apache.org/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.html

I didn't have much luck with the property, but it's worth a shot.

Show
Joseph LaFata added a comment - Java tries to use IPv6 if available. A problem can occur if your network doesn't support IPv6. The problem is described more in depth here: http://activemq.apache.org/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.html I didn't have much luck with the property, but it's worth a shot.
Hide
Permalink
Hiro Asari added a comment -

As described in the link Joseph shared, -J-Djava.net.preferIPv4Stack=true will force binding to 0.0.0.0.

Show
Hiro Asari added a comment - As described in the link Joseph shared, -J-Djava.net.preferIPv4Stack=true will force binding to 0.0.0.0.

People

  • Assignee:
    Hiro Asari
    Reporter:
    Eric M. Smith
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: