4 Replies Latest reply on Sep 23, 2013 5:20 AM by erasmo2 marciano2

    Bind address (-b) not working with 7.1.3

    Alexander Hartner Expert

      When starting JBoss 7.1.3 using the following command:

      standalone.bat -c standalone-full-ha.xml -b 127.0.0.1 -u 233.0.0.137 -Djboss.server.base.dir=%JBOSS_HOME%\standalone -Djboss.node.name=node1 -Djboss.socket.binding.port-offset=0

      The bind address parameter seems to be ignored on Windows. Using 7.2 the parameter works correctly.

      ss-as-7.1.3.Final\bin>standalone.bat -c standalone-full-ha.xml -b 127.0.0.1 -u 233.0.0.137 -Djboss.server.base.dir=\standalone -Djboss.node.name=node1 -Djboss.socket.binding.port-offset=0

      g "D:\jboss-as-7.1.3.Final\bin\standalone.conf.bat"

      =========================================================================

       

      s Bootstrap Environment

       

      S_HOME: D:\jboss-as-7.1.3.Final

       

      : C:\Program Files\Java\jdk1.7.0_25\bin\java

       

      _OPTS: -XX:+TieredCompilation -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs

      boss.byteman -Djboss.server.default.config=standalone.xml -Dxml.catalog.files=th:///dtd/thcatalog.cat -Dxml.catalog.verbosity=0 -Djboss.protocol.handler.modules=com.abchead.protocol -Dcom.abchead.protocol.th.debug=false -Dcom.abchead.util.debug.class=com.abchead.logging.Commons

      g -Dcom.abchead.protocol.th.datasource=java:/jdbc/abcheadDSNoTX -Djboss.protocol.handler.modules=com.abchead.protocol -Dhibernate.dialect=org.hibernate.dialect.SQLServerDialect -Dcom.abchead.protocol.th.debug=false -Dcom.abchead.util.debug.class=com.abchead.logging.Comm

      ging -Dxml.catalog.files=th:///dtd/thcatalog.cat -Dxml.catalog.verbosity=0 -Djboss.server.log.threshold=INFO

       

      =========================================================================

       

      09,660 INFO  [org.jboss.modules] JBoss Modules version 1.1.3.GA

      10,476 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      10,539 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.3.Final "Arges" starting

      14,144 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      14,153 INFO  [org.xnio] XNIO Version 3.0.6.GA

      14,163 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.6.GA

      14,174 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.8.SP1

      14,263 INFO  [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem

      14,268 INFO  [org.jboss.as.clustering.jgroups] JBAS010260: Activating JGroups subsystem.

      14,275 INFO  [org.jboss.as.osgi] JBAS011906: Activating OSGi Subsystem

      14,297 INFO  [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem

      14,319 INFO  [org.jboss.as.webservices] JBAS015537: Activating WebServices Extension

      14,346 INFO  [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.

      14,360 INFO  [org.jboss.as.jacorb] JBAS016300: Activating JacORB Subsystem

      14,418 INFO  [org.jboss.as.security] JBAS013171: Activating Security Subsystem

      14,363 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      14,620 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.13.Final

      14,736 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

      14,875 INFO  [org.jboss.jaxr] (MSC service thread 1-4) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

      14,958 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)

      15,032 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]

      15,160 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      15,247 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) JBAS010404: Deploying non-JDBC-compliant driver class net.sourceforge.jtds.jdbc.Driver (version 1.3)

      15,510 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 39) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

      15,523 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 39) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

      15,777 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on 0.0.0.0:4447

      15,790 WARN  [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

      15,826 INFO  [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-1) Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009

      15,828 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-/0.0.0.0:8080

      15,916 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=D:\jboss-as-7.1.3.Final\standalone\data\messagingjournal,bindingsDirectory=D:\j

      s-7.1.3.Final\standalone\data\messagingbindings,largeMessagesDirectory=D:\jboss-as-7.1.3.Final\standalone\data\messaginglargemessages,pagingDirectory=D:\jboss-as-7.1.3.Final\standalone\data\messagingpaging)

      15,929 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) Waiting to obtain live lock

      15,988 INFO  [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-5) Using NIO Journal

      16,019 WARN  [jacorb.codeset] (MSC service thread 1-4) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

      16,101 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started

      16,151 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-5) Waiting to obtain live lock

      16,151 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-5) Live Server Obtained live lock

      16,156 INFO  [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 64) Initializing mod_cluster 1.2.1.Final

      16,188 INFO  [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (ServerService Thread Pool -- 64) Listening to proxy advertisements on 224.0.1.105:23,364

      16,201 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      16,280 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started

      16,557 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/abcheadDSNoTX]

      16,561 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:/jdbc/abcheadDSECF]

      16,595 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:/jdbc/abcheadDS]

      17,382 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0:9999

      17,371 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "abcheadEJB.ear"

      17,365 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory D:\jboss-as-7.1.3.Final\standalone\deployments

      17,117 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-5) Started Netty Acceptor version 3.2.6.Final-20df069 0.0.0.0:5445 for CORE protocol

      17,054 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.5.GA

      23,817 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-5) Started Netty Acceptor version 3.2.6.Final-20df069 0.0.0.0:5455 for CORE protocol

      23,825 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) Server is now live

      23,825 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) HornetQ Server version 2.2.21.SNAPSHOT (HQ_2_2_21_final, 122) [c60302e6-1b95-11e3-a31d-0193037923ae]) started

      23,854 INFO  [org.hornetq.jms.server.impl.JMSServerManagerImpl] (ServerService Thread Pool -- 64) Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "Maggie". If this new address is incorrect please manually configure the connector to use the proper one.

      23,898 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

      23,912 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

      23,945 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-7) JBAS010406: Registered connection factory java:/JmsXA

      23,947 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/jms/ABCJMSConnectionFactory

      23,967 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-4) HornetQ resource adaptor started

      23,971 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorABCJMSConnectionFactory

      23,975 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/jms/ABCJMSConnectionFactory]

      23,993 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-7) HornetQ resource adaptor started

      23,994 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-7) IJ020002: Deployed: file://RaActivatorhornetq-ra

      23,995 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

      Any pointers on how to get around this problem and specify the bind address.

        • 1. Re: Bind address (-b) not working with 7.1.3
          Tomaz Cerar Master

          I would say that you have modified socket-binding settings from default ones.

           

          can you post <socket-binding> section of standalone-full-ha.xml?

          • 2. Re: Re: Bind address (-b) not working with 7.1.3
            Alexander Hartner Expert

            <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

                    <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
                    <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
                    <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
                    <socket-binding name="ajp" port="8009"/>
                    <socket-binding name="http" port="8080"/>
                    <socket-binding name="https" port="8443"/>
                    <socket-binding name="jacorb" interface="unsecure" port="3528"/>
                    <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
                    <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
                    <socket-binding name="jgroups-tcp" port="7600"/>
                    <socket-binding name="jgroups-tcp-fd" port="57600"/>
                    <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
                    <socket-binding name="jgroups-udp-fd" port="54200"/>
                    <socket-binding name="messaging" port="5445"/>
                    <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
                    <socket-binding name="messaging-throughput" port="5455"/>
                    <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364"/>
                    <socket-binding name="osgi-http" interface="management" port="8090"/>
                    <socket-binding name="remoting" port="4447"/>
                    <socket-binding name="txn-recovery-environment" port="4712"/>
                    <socket-binding name="txn-status-manager" port="4713"/>
                    <outbound-socket-binding name="mail-smtp">
                        <remote-destination host="localhost" port="25"/>
                    </outbound-socket-binding>
                </socket-binding-group>

            • 3. Re: Bind address (-b) not working with 7.1.3
              xiang yingbing Master

              I met the same problem with jboss 7.1.3, you must specify the concrete IP address instead of 0.0.0.0 or 127.0.0.1 !

               

              For example: standalone.bat -c standalone-full-ha.xml -b 192.168.12.23

               

              jboss 7.2.0 is perfect!

              • 4. Re: Bind address (-b) not working with 7.1.3
                erasmo2 marciano2 Master

                I too have same problem with  7.1.1.Final AS Certified Java EE 6 Full Profile

                 

                 

                But I don't problem with 6.1.0 Final EAP built from AS 7.2