Starting AS 7.1.1 with lo2 (127.0.0.2) as bind address: [g@:/opt/jboss]% ./bin/standalone.sh -b lo2 shows: 16:14:35,335 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-lo2-127.0.0.2-8080 Starting JDG 6 CR0 with the same shows: 16:10:21,030 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080 ... 16:10:21,731 DEBUG [org.infinispan.server.hotrod.HotRodServer] (MSC service thread 1-2) Starting server with basic settings: host=127.0.0.1, port=11222, masterThreads=-1, workerThreads=8, idleTimeout=-1, tcpNoDelay=true, sendBufSize=0, recvBufSize=0 ... server.log:788:16:10:21,731 DEBUG [org.infinispan.server.memcached.MemcachedServer] (MSC service thread 1-5) Starting server with basic settings: host=127.0.0.1, port=11211, masterThreads=-1, workerThreads=8, idleTimeout=-1, tcpNoDelay=true, sendBufSize=0, recvBufSize=0 So, JDG is ignoring the bind address passed for several subsystems. The only one where lo2 is being accepted is for the remoting connector for jmx.
Because of https://bugzilla.redhat.com/show_bug.cgi?id=818031 the endpoints are bound by default on the management interface. You can either use -Djboss.bind.address.management=lo2 or change the interface on the socket-binding for the appropriate protocols. I know it's not ideal
*** Bug 829807 has been marked as a duplicate of this bug. ***
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Tristan will describe...
I disagree with this issue being part of the release notes, but I'll add a Tech note anyway to clarify.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,5 @@ -Tristan will describe...+The JDG server by default binds its listening ports to the loopback address (127.0.0.1). The -b switch can be used to modify the address on which to bind the "public" interface. However, since the JDG endpoints are bound to the "management" interface for security reasons, the -b switch does not affect them. The user should modify the standalone.xml configuration file to place the endpoints on the public interface: + +<socket-binding name="hotrod" interface="public" port="11222"/> + +After the above modification, the -b switch will determine the network address on which the hotrod port will be bound.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,5 +1,8 @@ -The JDG server by default binds its listening ports to the loopback address (127.0.0.1). The -b switch can be used to modify the address on which to bind the "public" interface. However, since the JDG endpoints are bound to the "management" interface for security reasons, the -b switch does not affect them. The user should modify the standalone.xml configuration file to place the endpoints on the public interface: +The JBoss Data Grid server by default binds its listening ports to a loopback address (<literal>127.0.0.1</literal>). The <literal>-b</literal> switch can be used to modify the address on which to bind the public interface. However, since the JBoss Data Grid endpoints are bound to the management interface for security reasons, the <literal>-b</literal> switch does not affect them. The user should modify the <filename>standalone.xml</filename> configuration file to place the endpoints on the public interface: +</papa> -<socket-binding name="hotrod" interface="public" port="11222"/> +<programlisting> - +<![CDATA[<socket-binding name="hotrod" interface="public" port="11222"/>]]> -After the above modification, the -b switch will determine the network address on which the hotrod port will be bound.+</programlisting> +<para> +After the above modification, the <literal>-b</literal> switch will determine the network address on which the hot rod port will be bound.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,5 +1,5 @@ The JBoss Data Grid server by default binds its listening ports to a loopback address (<literal>127.0.0.1</literal>). The <literal>-b</literal> switch can be used to modify the address on which to bind the public interface. However, since the JBoss Data Grid endpoints are bound to the management interface for security reasons, the <literal>-b</literal> switch does not affect them. The user should modify the <filename>standalone.xml</filename> configuration file to place the endpoints on the public interface: -</papa> +</para> <programlisting> <![CDATA[<socket-binding name="hotrod" interface="public" port="11222"/>]]>
This will be fixed by https://bugzilla.redhat.com/show_bug.cgi?id=875736
ttarrant will add jira links as appropriate.