IPV6 support not available

[sholla]

Expected behavior

If broker is configured to bind to ::1 or other IpV6 addresses, it should bind to the relevant address in that space.
Tell us what should happen
The broker and related should run correctly binding to the relevant IpV6 address

Actual behavior

Exception since protocol family is not supported.
Tell us what happens instead
Following exception occurs when running "pulsar standalone"
2017-12-10 17:10:36,026 - INFO - [main:ContextHandler@781] - Started o.e.j.s.ServletContextHandler@779de014{/ws/reader,null,AVAILABLE}
2017-12-10 17:10:36,026 - INFO - [main:ContextHandler@781] - Started o.e.j.s.h.ContextHandler@5c41d037{/static,null,AVAILABLE}
2017-12-10 17:10:36,028 - ERROR - [main:PulsarService@342] - java.net.SocketException: Protocol family unavailable
org.apache.pulsar.broker.PulsarServerException: java.net.SocketException: Protocol family unavailable
at org.apache.pulsar.broker.web.WebService.start(WebService.java:215)
at org.apache.pulsar.broker.PulsarService.start(PulsarService.java:331)
at org.apache.pulsar.PulsarStandaloneStarter.start(PulsarStandaloneStarter.java:164)
at org.apache.pulsar.PulsarStandaloneStarter.main(PulsarStandaloneStarter.java:209)
Caused by: java.net.SocketException: Protocol family unavailable
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:317)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:390)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.apache.pulsar.broker.web.WebService.start(WebService.java:211)
... 3 more
Exception in thread "main" org.apache.pulsar.broker.PulsarServerException: org.apache.pulsar.broker.PulsarServerException: java.net.SocketException: Protocol family unavailable
at org.apache.pulsar.broker.PulsarService.start(PulsarService.java:343)
at org.apache.pulsar.PulsarStandaloneStarter.start(PulsarStandaloneStarter.java:164)
at org.apache.pulsar.PulsarStandaloneStarter.main(PulsarStandaloneStarter.java:209)
Caused by: org.apache.pulsar.broker.PulsarServerException: java.net.SocketException: Protocol family unavailable
at org.apache.pulsar.broker.web.WebService.start(WebService.java:215)
at org.apache.pulsar.broker.PulsarService.start(PulsarService.java:331)
... 2 more
Caused by: java.net.SocketException: Protocol family unavailable
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:317)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:390)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.apache.pulsar.broker.web.WebService.start(WebService.java:211)
... 3 more

Steps to reproduce

How can we reproduce the issue
I have tried it with the standalone configuration(conf/standalone.conf) by setting bindAddress=::1 when the above exception occurs.

System configuration

Pulsar version: x.y
1.20

[merlimat]

Thanks for reporting this @sholla. It looks like Jetty is not able to bind on IPv6 but netty server on 6650. Will try to get a fix soon.

[sholla]

ok @merlimat . Shall await then.

[sijie]

I think this is related to #1949