1 2 3 Previous Next 31 Replies Latest reply on Apr 14, 2015 5:39 AM by kiran naikwade

    Jboss application not working in cluster in standalone mode.

    Abhishek Sharma Newbie

      12:39:52,026 INFO  [stdout] (pool-14-thread-1)

      12:39:52,026 INFO  [stdout] (pool-14-thread-1) -------------------------------------------------------------------

      12:39:52,026 INFO  [stdout] (pool-14-thread-1) GMS: address=dell-pc/web, cluster=web, physical address=0.0.0.0:55300

      12:39:52,036 INFO  [stdout] (pool-14-thread-1) -------------------------------------------------------------------

       

       

      12:39:52,046 SEVERE [org.jgroups.protocols.UDP] (OOB-1,null) failed sending message to dell-pc/web (100 bytes): java.lang.Exception: dest=0.0.0.0/0.0.0.0:55300 (103 bytes), cause: java.net.BindException: Cannot assign requested address: Datagram send failed

      12:39:54,526 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

      12:39:54,528 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

      12:39:54,695 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000078: Starting JGroups Channel

      12:39:54,705 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000094: Received new cluster view: [dell-pc/web|0] [dell-pc/web]

       

       

      I see my Jboss is up and running but not able to access my application. Can someone pick this and help me out.

        • 1. Re: Jboss application not working in cluster in standalone mode.
          Jay SenSharma Master

          From your output it looks like you are running your JBoss on bind address 0.0.0.0,  For JGroups that is not correct  and hence it is causing the error.

           

          GMS: address=dell-pc/web, cluster=web, physical address=0.0.0.0:55300
          
          
          

           

          Can you try running your JBoss on a specific IP Address.     Like ./standalone.sh  -c standalone-ha.xml  -b 10.10.10.10

           

           

           

          If you can not run your whole JBoss on on specific IP Address then at least run the jgroups  on a particular IP Address, by adding a new interface listening to a particular Address inside the  <interfaces> tag. The you can use the ""

           

          <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688" interface="your_interface_name"  />
          <socket-binding name="jgroups-udp-fd" port="54200" interface="your_interface_name" />
          
          
          

           

           

          [standalone@localhost:9999 /] /socket-binding-group=standard-sockets/socket-binding=jgroups-udp:write-attribute(name=interface, value="your_interface_name")
          [standalone@localhost:9999 /] /socket-binding-group=standard-sockets/socket-binding=jgroups-udp-fd:write-attribute(name=interface, value="your_interface_name")
          
          
          
          • 2. Re: Jboss application not working in cluster in standalone mode.
            Abhishek Sharma Newbie

            Do I have to define "-b" in order to start my jboss in clustered mode. .I want to ignore that in fact. Coz as explained above adding interface="your_interface_name is obstructing my jboss coming up.

            • 3. Re: Re: Jboss application not working in cluster in standalone mode.
              Jay SenSharma Master

              Abhishek,

               

                You can either run your JBoss/WildFly using  ./standalone.sh  -c standalone-ha.xml  -b 10.10.10.10   so that apart from management interface all the other services like remoting/jgroups ..etc will be using the public interface address as "10.10.10.10"


                (OR)

               

                  Your should configure the interface as following steps:

               

              1. Configure a new interface with name "your_interface_name" as following:

                   <interfaces>
                      <interface name="management">
                          <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
                      </interface>
                      <interface name="public">
                          <inet-address value="${jboss.bind.address:127.0.0.1}"/>
                      </interface>
                      <interface name="unsecure">
                          <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
                      </interface>
              
                      <interface name="your_interface_name">
                          <inet-address value="10.10.10.10"/>        <!-- Assuming you want to run oyur jgroup components in this address -->
                      </interface>
                  </interfaces>
              
              
              

               

              2. Now you should define the interface name "your_interface_name" to whatever socket bindings you want, In your case it might be related to all the jgroups socket bindings. Example:

                  <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688" interface="your_interface_name"  /> 
                  <socket-binding name="jgroups-udp-fd" port="54200" interface="your_interface_name" />
                    .
                    .
              
              

               

               

              Please post the new errors which you are getting, that will give us more idea.

              • 4. Re: Re: Jboss application not working in cluster in standalone mode.
                Abhishek Sharma Newbie

                Thanks Jay for the swift response.

                 

                 

                 

                 

                <interface name="your_interface_name"> 

                            <inet-address value="10.10.10.10"/>      

                        </interface> 

                 

                 

                    </interfaces>

                 

                 

                    <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="81"/>

                        <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-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/>

                        <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" interface="your_interface_name" />

                        <socket-binding name="jgroups-udp-fd" port="54200" interface="your_interface_name"/>

                 

                 

                The following is the error I received :

                 

                 

                12:44:38,116 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.network.your_interface_name: org.jboss.msc.service.StartException in service jboss.network.your_interface_name: JBAS015810: failed to resolve interface your_interface_name

                  at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]

                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]

                  at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]

                • 5. Re: Re: Jboss application not working in cluster in standalone mode.
                  Jay SenSharma Master

                  Abhishek,

                   

                     The error which you are getting indicates that you have simply used my example address "10.10.10.10" in your configuration,  Where as it should be replaced with your IPAddress.

                   

                     Just run the "ifconfig" (in Linux) command to find your IPAddress and replace my 10.10.10.10 address with that.  For Windows use (ipconfig) to find your IPAddress.

                  • 6. Re: Re: Jboss application not working in cluster in standalone mode.
                    Abhishek Sharma Newbie

                    I have used the following command to start the Jboss and still i can see the following error.

                     

                    Command Used : C:\Abhi1\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin>standalone.bat -c standalone-ha.xml -b <My IP address>

                     

                     

                    14:22:47,150 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "glog-ear.ear"

                    14:22:47,593 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.network.your_interface_name: org.jboss.msc.service.StartException in service jboss.network.your_interface_name: JBAS015810: failed to resolve interface your_interface_name

                      at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]

                      at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]

                    • 7. Re: Re: Re: Jboss application not working in cluster in standalone mode.
                      Jay SenSharma Master

                      Abhishek,

                      Can you paste your standalone-ha.xml here,  Because i am suspecting that yoiu might have not entered a valid IP Address in the section, One can reproduce the same error  just by specifying an incorrect inet-address inside the interface section.

                       

                      MSC00001: Failed to start service jboss.network.your_interface_name: org.jboss.msc.service.StartException in service jboss.network.your_interface_name: JBAS015810: failed to resolve interface your_interface_name
                      
                      

                       

                              <interface name="your_interface_name">
                                  <inet-address value="10.10.10.10"/>    <!-- Some incorrect value here should cause JBAS015810 -->
                              </interface>
                      
                      
                      • 8. Re: Re: Jboss application not working in cluster in standalone mode.
                        Abhishek Sharma Newbie

                        Sorry I have not changed it in the xml file so got the error message. Will be tuning it.........

                        • 9. Re: Re: Jboss application not working in cluster in standalone mode.
                          Abhishek Sharma Newbie

                          This is what i have received in the logs.

                           

                           

                          14:31:31,407 INFO  [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory

                          14:31:31,417 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

                          14:31:31,478 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "ClusterWebApp.war"

                          14:31:31,478 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "glog-ear.ear"

                          14:31:32,356 INFO  [stdout] (pool-13-thread-1)

                          14:31:32,356 INFO  [stdout] (pool-13-thread-1) -------------------------------------------------------------------

                          14:31:32,356 INFO  [stdout] (pool-13-thread-1) GMS: address=dell-pc/web, cluster=web, physical address=192.168.0.118:55200

                          14:31:32,356 INFO  [stdout] (pool-13-thread-1) -------------------------------------------------------------------

                           

                           

                          14:31:34,840 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:34,843 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:34,990 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000078: Starting JGroups Channel

                          14:31:35,000 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000094: Received new cluster view: [dell-pc/web|0] [dell-pc/web]

                          14:31:35,020 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000079: Cache local address is dell-pc/web, physical addresses are [192.168.0.118:55200]

                          14:31:35,030 INFO  [org.infinispan.factories.GlobalComponentRegistry] (pool-14-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL

                          14:31:35,040 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (pool-14-thread-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:35,355 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-14-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

                          14:31:35,404 INFO  [org.jboss.as.clustering.infinispan] (pool-14-thread-1) JBAS010281: Started repl cache from web container

                          14:31:35,434 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (MSC service thread 1-8) JBAS010206: Number of cluster members: 1

                          14:31:35,572 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:35,577 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:35,648 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-6) ISPN000031: MBeans were successfully registered to the platform mbean server.

                          14:31:35,677 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-6) JBAS010281: Started //default-host//ClusterWebApp cache from web container

                          14:31:35,700 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:35,700 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                          14:31:36,026 INFO  [org.jboss.web] (MSC service thread 1-6) JBAS018210: Registering web context: /ClusterWebApp

                          14:31:36,972 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-api.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:36,972 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:36,972 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr173_1.0_api.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:36,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb1-impl.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:36,992 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "integration_transmitter-1.0.0.jar"

                          14:31:36,992 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "integration_receiver-1.0.0.jar"

                          14:31:36,992 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "ui-1.0.0.war"

                          14:31:36,992 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "business-1.0.0.jar"

                          14:31:36,992 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "service-1.0.0.jar"

                          14:31:36,992 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "persistence-1.0.0.jar"

                          14:31:37,042 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/hibernate-commons-annotations-3.3.0.ga.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,042 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/hibernate-3.2.1.ga.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,042 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/ehcache-1.6.0.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,052 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/asm-attrs-1.5.3.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,052 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/antlr-2.7.6.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,052 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/cglib-2.1_3.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,052 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/asm-1.5.3.jar in "/C:/Abhi1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                          14:31:37,102 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'

                          14:31:37,102 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'

                          14:31:37,352 INFO  [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011401: Read persistence.xml for LogitDatasourceV2

                          14:31:37,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

                          14:31:37,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

                          14:31:37,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.xml.bind:main") which may be changed or removed in future versions without notice.

                          14:31:37,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.xml.bind:main") which may be changed or removed in future versions without notice.

                          14:31:37,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("net.sourceforge.nekohtml:main") which may be changed or removed in future versions without notice.

                          14:31:37,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("net.sourceforge.nekohtml:main") which may be changed or removed in future versions without notice.

                          14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("nu.xom:main") which may be changed or removed in future versions without notice.

                          14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("nu.xom:main") which may be changed or removed in future versions without notice.

                          14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.

                          14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.

                          14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.log4j:main") which may be changed or removed in future versions without notice.

                          14:31:37,616 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.log4j:main") which may be changed or removed in future versions without notice.

                          14:31:37,616 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice.

                          14:31:37,616 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice.

                          14:31:37,616 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice.

                          14:31:37,616 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice.

                          14:31:37,616 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.as.web:main") which may be changed or removed in future versions without notice.

                          14:31:37,626 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.as.web:main") which may be changed or removed in future versions without notice.

                          14:31:37,626 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.osgi.framework:main") which may be changed or removed in future versions without notice.

                          14:31:37,626 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.osgi.framework:main") which may be changed or removed in future versions without notice.

                           

                           

                          If we see the below

                           

                          14:31:35,000 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000094: Received new cluster view: [dell-pc/web|0] [dell-pc/web]

                           

                           

                          here [dell-pc/web|1] should populate if i am not wrong which in fact not happened. I am really worried what is going wrong. Does the second Jboss instance shoould be up and running while achieving this.

                          • 10. Re: Re: Jboss application not working in cluster in standalone mode.
                            Abhishek Sharma Newbie

                            Also here is my standalone-ha.xml below :

                             

                            <?xml version='1.0' encoding='UTF-8'?>

                             

                             

                            <server xmlns="urn:jboss:domain:1.2">

                             

                             

                                <extensions>

                                    <extension module="org.jboss.as.clustering.infinispan"/>

                                    <extension module="org.jboss.as.clustering.jgroups"/>

                                    <extension module="org.jboss.as.cmp"/>

                                    <extension module="org.jboss.as.configadmin"/>

                                    <extension module="org.jboss.as.connector"/>

                                    <extension module="org.jboss.as.deployment-scanner"/>

                                    <extension module="org.jboss.as.ee"/>

                                    <extension module="org.jboss.as.ejb3"/>

                                    <extension module="org.jboss.as.jacorb"/>

                                    <extension module="org.jboss.as.jaxr"/>

                                    <extension module="org.jboss.as.jaxrs"/>

                                    <extension module="org.jboss.as.jdr"/>

                                    <extension module="org.jboss.as.jmx"/>

                                    <extension module="org.jboss.as.jpa"/>

                                    <extension module="org.jboss.as.jsr77"/>

                                    <extension module="org.jboss.as.logging"/>

                                    <extension module="org.jboss.as.mail"/>

                                    <extension module="org.jboss.as.messaging"/>

                                    <extension module="org.jboss.as.modcluster"/>

                                    <extension module="org.jboss.as.naming"/>

                                    <extension module="org.jboss.as.osgi"/>

                                    <extension module="org.jboss.as.pojo"/>

                                    <extension module="org.jboss.as.remoting"/>

                                    <extension module="org.jboss.as.sar"/>

                                    <extension module="org.jboss.as.security"/>

                                    <extension module="org.jboss.as.threads"/>

                                    <extension module="org.jboss.as.transactions"/>

                                    <extension module="org.jboss.as.web"/>

                                    <extension module="org.jboss.as.webservices"/>

                                    <extension module="org.jboss.as.weld"/>

                                </extensions>

                             

                             

                                <management>

                                    <security-realms>

                                        <security-realm name="ManagementRealm">

                                            <authentication>

                                                <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>

                                            </authentication>

                                        </security-realm>

                                        <security-realm name="ApplicationRealm">

                                            <authentication>

                                                <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>

                                            </authentication>

                                        </security-realm>

                                    </security-realms>

                                    <management-interfaces>

                                        <native-interface security-realm="ManagementRealm">

                                            <socket-binding native="management-native"/>

                                        </native-interface>

                                        <http-interface security-realm="ManagementRealm">

                                            <socket-binding http="management-http"/>

                                        </http-interface>

                                    </management-interfaces>

                                </management>

                             

                             

                                <profile>

                                    <subsystem xmlns="urn:jboss:domain:logging:1.1">

                                        <console-handler name="CONSOLE">

                                            <level name="INFO"/>

                                            <formatter>

                                                <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>

                                            </formatter>

                                        </console-handler>

                                        <periodic-rotating-file-handler name="FILE">

                                            <formatter>

                                                <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>

                                            </formatter>

                                            <file relative-to="jboss.server.log.dir" path="server.log"/>

                                            <suffix value=".yyyy-MM-dd"/>

                                            <append value="true"/>

                                        </periodic-rotating-file-handler>

                                        <logger category="com.arjuna">

                                            <level name="WARN"/>

                                        </logger>

                                        <logger category="org.apache.tomcat.util.modeler">

                                            <level name="WARN"/>

                                        </logger>

                                        <logger category="sun.rmi">

                                            <level name="WARN"/>

                                        </logger>

                                        <logger category="jacorb">

                                            <level name="WARN"/>

                                        </logger>

                                        <logger category="jacorb.config">

                                            <level name="ERROR"/>

                                        </logger>

                                        <root-logger>

                                            <level name="INFO"/>

                                            <handlers>

                                                <handler name="CONSOLE"/>

                                                <handler name="FILE"/>

                                            </handlers>

                                        </root-logger>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:cmp:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:configadmin:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:datasources:1.0">

                                        <datasources>

                                            <datasource jndi-name="java:jboss/datasources/Logit-DS" pool-name="Logit-DS" enabled="true" use-java-context="true">

                                                <connection-url>jdbc:jtds:sqlserver://localhost:1433/DHL_JB7;loginTimeout=30</connection-url>

                                                <driver>jtds</driver>

                                                <security>

                                                    <user-name>DHL</user-name>

                                                    <password>K_zo83TBT</password>

                                                </security>

                                            </datasource>

                                            <drivers>

                                                <driver name="jtds" module="net.sourceforge.jtds">

                             

                             

                                                    <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

                                                </driver>

                                            </drivers>

                                        </datasources>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">

                                        <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:ee:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:ejb3:1.2">

                                        <session-bean>

                                            <stateless>

                                                <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>

                                            </stateless>

                                            <stateful default-access-timeout="5000" cache-ref="simple" clustered-cache-ref="clustered"/>

                                            <singleton default-access-timeout="5000"/>

                                        </session-bean>

                                        <mdb>

                                            <resource-adapter-ref resource-adapter-name="hornetq-ra"/>

                                            <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>

                                        </mdb>

                                        <pools>

                                            <bean-instance-pools>

                                                <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>

                                                <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>

                                            </bean-instance-pools>

                                        </pools>

                                        <caches>

                                            <cache name="simple" aliases="NoPassivationCache"/>

                                            <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>

                                            <cache name="clustered" passivation-store-ref="infinispan" aliases="StatefulTreeCache"/>

                                        </caches>

                                        <passivation-stores>

                                            <file-passivation-store name="file"/>

                                            <cluster-passivation-store name="infinispan" cache-container="ejb"/>

                                        </passivation-stores>

                                        <async thread-pool-name="default"/>

                                        <timer-service thread-pool-name="default">

                                            <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>

                                        </timer-service>

                                        <remote connector-ref="remoting-connector" thread-pool-name="default"/>

                                        <thread-pools>

                                            <thread-pool name="default">

                                                <max-threads count="10"/>

                                                <keepalive-time time="100" unit="milliseconds"/>

                                            </thread-pool>

                                        </thread-pools>

                                        <iiop enable-by-default="false" use-qualified-name="false"/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="cluster">

                                        <cache-container name="cluster" aliases="ha-partition" default-cache="default">

                                            <transport lock-timeout="60000"/>

                                            <replicated-cache name="default" mode="SYNC" batching="true">

                                                <locking isolation="REPEATABLE_READ"/>

                                            </replicated-cache>

                                        </cache-container>

                                        <cache-container name="web" aliases="standard-session-cache" default-cache="repl">

                                            <transport lock-timeout="60000"/>

                                            <replicated-cache name="repl" mode="ASYNC" batching="true">

                                                <file-store/>

                                            </replicated-cache>

                                            <replicated-cache name="sso" mode="SYNC" batching="true"/>

                                            <distributed-cache name="dist" mode="ASYNC" batching="true">

                                                <file-store/>

                                            </distributed-cache>

                                        </cache-container>

                                        <cache-container name="ejb" aliases="sfsb sfsb-cache" default-cache="repl">

                                            <transport lock-timeout="60000"/>

                                            <replicated-cache name="repl" mode="ASYNC" batching="true">

                                                <eviction strategy="LRU"/>

                                                <file-store/>

                                            </replicated-cache>

                                            <replicated-cache name="remote-connector-client-mappings" mode="SYNC" batching="true"/>

                                            <distributed-cache name="dist" mode="ASYNC" batching="true">

                                                <eviction strategy="LRU"/>

                                                <file-store/>

                                            </distributed-cache>

                                        </cache-container>

                                        <cache-container name="hibernate" default-cache="local-query">

                                            <transport lock-timeout="60000"/>

                                            <local-cache name="local-query">

                                                <transaction mode="NONE"/>

                                                <eviction strategy="LRU" max-entries="10000"/>

                                                <expiration max-idle="100000"/>

                                            </local-cache>

                                            <invalidation-cache name="entity" mode="SYNC">

                                                <transaction mode="NON_XA"/>

                                                <eviction strategy="LRU" max-entries="10000"/>

                                                <expiration max-idle="100000"/>

                                            </invalidation-cache>

                                            <replicated-cache name="timestamps" mode="ASYNC">

                                                <transaction mode="NONE"/>

                                                <eviction strategy="NONE"/>

                                            </replicated-cache>

                                        </cache-container>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jacorb:1.1">

                                        <orb>

                                            <initializers security="on" transactions="spec"/>

                                        </orb>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jaxr:1.1">

                                        <connection-factory jndi-name="java:jboss/jaxr/ConnectionFactory"/>

                                        <properties/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:jca:1.1">

                                        <archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/>

                                        <bean-validation enabled="true"/>

                                        <default-workmanager>

                                            <short-running-threads>

                                                <core-threads count="50"/>

                                                <queue-length count="50"/>

                                                <max-threads count="50"/>

                                                <keepalive-time time="10" unit="seconds"/>

                                            </short-running-threads>

                                            <long-running-threads>

                                                <core-threads count="50"/>

                                                <queue-length count="50"/>

                                                <max-threads count="50"/>

                                                <keepalive-time time="10" unit="seconds"/>

                                            </long-running-threads>

                                        </default-workmanager>

                                        <cached-connection-manager/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jdr:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="udp">

                                        <stack name="udp">

                                            <transport type="UDP" socket-binding="jgroups-udp" diagnostics-socket-binding="jgroups-diagnostics"/>

                                            <protocol type="PING"/>

                                            <protocol type="MERGE2"/>

                                            <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>

                                            <protocol type="FD"/>

                                            <protocol type="VERIFY_SUSPECT"/>

                                            <protocol type="BARRIER"/>

                                            <protocol type="pbcast.NAKACK"/>

                                            <protocol type="UNICAST2"/>

                                            <protocol type="pbcast.STABLE"/>

                                            <protocol type="pbcast.GMS"/>

                                            <protocol type="UFC"/>

                                            <protocol type="MFC"/>

                                            <protocol type="FRAG2"/>

                                        </stack>

                                        <stack name="tcp">

                                            <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/>

                                            <protocol type="MPING" socket-binding="jgroups-mping"/>

                                            <protocol type="MERGE2"/>

                                            <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>

                                            <protocol type="FD"/>

                                            <protocol type="VERIFY_SUSPECT"/>

                                            <protocol type="BARRIER"/>

                                            <protocol type="pbcast.NAKACK"/>

                                            <protocol type="UNICAST2"/>

                                            <protocol type="pbcast.STABLE"/>

                                            <protocol type="pbcast.GMS"/>

                                            <protocol type="UFC"/>

                                            <protocol type="MFC"/>

                                            <protocol type="FRAG2"/>

                                        </stack>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jmx:1.1">

                                        <show-model value="true"/>

                                        <remoting-connector/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jpa:1.0">

                                        <jpa default-datasource=""/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:jsr77:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:mail:1.0">

                                        <mail-session jndi-name="java:jboss/mail/Default">

                                            <smtp-server outbound-socket-binding-ref="mail-smtp"/>

                                        </mail-session>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:messaging:1.1">

                                        <hornetq-server>

                                            <clustered>true</clustered>

                                            <persistence-enabled>true</persistence-enabled>

                                            <journal-file-size>102400</journal-file-size>

                                            <journal-min-files>2</journal-min-files>

                             

                             

                                            <connectors>

                                                <netty-connector name="netty" socket-binding="messaging"/>

                                                <netty-connector name="netty-throughput" socket-binding="messaging-throughput">

                                                    <param key="batch-delay" value="50"/>

                                                </netty-connector>

                                                <in-vm-connector name="in-vm" server-id="0"/>

                                            </connectors>

                             

                             

                                            <acceptors>

                                                <netty-acceptor name="netty" socket-binding="messaging"/>

                                                <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

                                                    <param key="batch-delay" value="50"/>

                                                    <param key="direct-deliver" value="false"/>

                                                </netty-acceptor>

                                                <in-vm-acceptor name="in-vm" server-id="0"/>

                                            </acceptors>

                             

                             

                                            <broadcast-groups>

                                                <broadcast-group name="bg-group1">

                                                    <group-address>231.7.7.7</group-address>

                                                    <group-port>9876</group-port>

                                                    <broadcast-period>5000</broadcast-period>

                                                    <connector-ref>

                                                        netty

                                                    </connector-ref>

                                                </broadcast-group>

                                            </broadcast-groups>

                             

                             

                                            <discovery-groups>

                                                <discovery-group name="dg-group1">

                                                    <group-address>231.7.7.7</group-address>

                                                    <group-port>9876</group-port>

                                                    <refresh-timeout>10000</refresh-timeout>

                                                </discovery-group>

                                            </discovery-groups>

                             

                             

                                            <cluster-connections>

                                                <cluster-connection name="my-cluster">

                                                    <address>jms</address>

                                                    <connector-ref>netty</connector-ref>

                                                    <discovery-group-ref discovery-group-name="dg-group1"/>

                                                </cluster-connection>

                                            </cluster-connections>

                             

                             

                                            <security-settings>

                                                <security-setting match="#">

                                                    <permission type="send" roles="guest"/>

                                                    <permission type="consume" roles="guest"/>

                                                    <permission type="createNonDurableQueue" roles="guest"/>

                                                    <permission type="deleteNonDurableQueue" roles="guest"/>

                                                </security-setting>

                                            </security-settings>

                             

                             

                                            <address-settings>

                                                <address-setting match="#">

                                                    <dead-letter-address>jms.queue.DLQ</dead-letter-address>

                                                    <expiry-address>jms.queue.ExpiryQueue</expiry-address>

                                                    <redelivery-delay>0</redelivery-delay>

                                                    <max-size-bytes>10485760</max-size-bytes>

                                                    <address-full-policy>BLOCK</address-full-policy>

                                                    <message-counter-history-day-limit>10</message-counter-history-day-limit>

                                                    <redistribution-delay>1000</redistribution-delay>

                                                </address-setting>

                                            </address-settings>

                             

                             

                                            <jms-connection-factories>

                                                <connection-factory name="InVmConnectionFactory">

                                                    <connectors>

                                                        <connector-ref connector-name="in-vm"/>

                                                    </connectors>

                                                    <entries>

                                                        <entry name="java:/ConnectionFactory"/>

                                                    </entries>

                                                </connection-factory>

                                                <connection-factory name="RemoteConnectionFactory">

                                                    <connectors>

                                                        <connector-ref connector-name="netty"/>

                                                    </connectors>

                                                    <entries>

                                                        <entry name="RemoteConnectionFactory"/>

                                                        <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>

                                                    </entries>

                                                </connection-factory>

                                                <pooled-connection-factory name="hornetq-ra">

                                                    <transaction mode="xa"/>

                                                    <connectors>

                                                        <connector-ref connector-name="in-vm"/>

                                                    </connectors>

                                                    <entries>

                                                        <entry name="java:/JmsXA"/>

                                                    </entries>

                                                </pooled-connection-factory>

                                            </jms-connection-factories>

                             

                             

                                            <jms-destinations>

                                                <jms-queue name="testQueue">

                                                    <entry name="queue/test"/>

                                                    <entry name="java:jboss/exported/jms/queue/test"/>

                                                </jms-queue>

                                                <jms-topic name="testTopic">

                                                    <entry name="topic/test"/>

                                                    <entry name="java:jboss/exported/jms/topic/test"/>

                                                </jms-topic>

                                            </jms-destinations>

                                        </hornetq-server>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

                                        <mod-cluster-config advertise-socket="modcluster">

                                            <dynamic-load-provider>

                                                <load-metric type="busyness"/>

                                            </dynamic-load-provider>

                                        </mod-cluster-config>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:naming:1.1"/>

                                    <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">

                                        <properties>

                                            <property name="org.osgi.framework.startlevel.beginning">

                                                1

                                            </property>

                                        </properties>

                                        <capabilities>

                                            <capability name="javax.servlet.api:v25"/>

                                            <capability name="javax.transaction.api"/>

                                            <capability name="org.apache.felix.log" startlevel="1"/>

                                            <capability name="org.jboss.osgi.logging" startlevel="1"/>

                                            <capability name="org.apache.felix.configadmin" startlevel="1"/>

                                            <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>

                                        </capabilities>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:pojo:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:remoting:1.1">

                                        <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:sar:1.0"/>

                                    <subsystem xmlns="urn:jboss:domain:security:1.1">

                                        <security-domains>

                                            <security-domain name="other" cache-type="default">

                                                <authentication>

                                                    <login-module code="Remoting" flag="optional">

                                                        <module-option name="password-stacking" value="useFirstPass"/>

                                                    </login-module>

                                                    <login-module code="RealmUsersRoles" flag="required">

                                                        <module-option name="usersProperties" value="${jboss.server.config.dir}/application-users.properties"/>

                                                        <module-option name="rolesProperties" value="${jboss.server.config.dir}/application-roles.properties"/>

                                                        <module-option name="realm" value="ApplicationRealm"/>

                                                        <module-option name="password-stacking" value="useFirstPass"/>

                                                    </login-module>

                                                </authentication>

                                            </security-domain>

                                            <security-domain name="jboss-web-policy" cache-type="default">

                                                <authorization>

                                                    <policy-module code="Delegating" flag="required"/>

                                                </authorization>

                                            </security-domain>

                                            <security-domain name="jboss-ejb-policy" cache-type="default">

                                                <authorization>

                                                    <policy-module code="Delegating" flag="required"/>

                                                </authorization>

                                            </security-domain>

                                        </security-domains>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:threads:1.1"/>

                                    <subsystem xmlns="urn:jboss:domain:transactions:1.1">

                                        <core-environment>

                                            <process-id>

                                                <uuid/>

                                            </process-id>

                                        </core-environment>

                                        <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>

                                        <coordinator-environment default-timeout="300"/>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="true">

                                        <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>

                                        <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp"/>

                                        <virtual-server name="default-host" enable-welcome-root="true">

                                            <alias name="localhost"/>

                                            <alias name="example.com"/>

                                        </virtual-server>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:webservices:1.1">

                                        <modify-wsdl-address>true</modify-wsdl-address>

                                        <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>

                                        <endpoint-config name="Standard-Endpoint-Config"/>

                                        <endpoint-config name="Recording-Endpoint-Config">

                                            <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">

                                                <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>

                                            </pre-handler-chain>

                                        </endpoint-config>

                                    </subsystem>

                                    <subsystem xmlns="urn:jboss:domain:weld:1.0"/>

                                </profile>

                             

                             

                                <interfaces>

                                    <interface name="management">

                                        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>

                                    </interface>

                                    <interface name="public">

                                        <inet-address value="${jboss.bind.address:127.0.0.1}"/>

                                    </interface>

                                    <interface name="unsecure">

                                        <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>

                                    </interface>

                             

                             

                              <interface name="OceanView"> 

                                        <inet-address value="192.168.0.118"/>        <!-- Assuming you want to run oyur jgroup components in this address --> 

                                    </interface> 

                             

                             

                                </interfaces>

                             

                             

                                <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="81"/>

                                    <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-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/>

                                    <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" interface="OceanView" />

                                    <socket-binding name="jgroups-udp-fd" port="54200" interface="OceanView"/>

                                    <socket-binding name="messaging" port="5445"/>

                                    <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>

                             

                             

                            </server>

                            • 11. Re: Re: Re: Jboss application not working in cluster in standalone mode.
                              Jay SenSharma Master

                              So now we see that all the Errors are gone , you are no longer seeing any of the following error:

                               

                              SEVERE [org.jgroups.protocols.UDP] (OOB-1,null) failed sending message to dell-pc/web (100 bytes): java.lang.Exception: dest=0.0.0.0/0.0.0.0:55300 (103 bytes), cause: java.net.BindException: Cannot assign requested address: Datagram send failed
                              

                               

                              and

                               

                              12:44:38,116 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.network.your_interface_name: org.jboss.msc.service.StartException in service jboss.network.your_interface_name: JBAS015810: failed to resolve interface your_interface_name
                              

                               

                               

                              Now we see that your cluster view as >>>  Received new cluster view: [dell-pc/web|0] [dell-pc/web],  Which means that only one JBoss instance (the current one) is in the cluster.   So if you will start your other jboss ha profiles with the same multicast address then you should see that they will be forming the cluster and the  [cluster view]  will show more instances in the cluster formation.

                              • 12. Re: Re: Re: Jboss application not working in cluster in standalone mode.
                                Jay SenSharma Master

                                And regarding the WARN messages [JBAS018567]  which are appearing in your logs:

                                 

                                If any Module which is provided by JBoss is marked as "private" like following then you should not be using it because It's private and in next releases of JBoss it might be changed or removed or new version of these jars might be introduced (which might or might not be suitable for your application which is referring to it).  So rather than using "private" modules you should create your own custom module and use it in your application.

                                 

                                <module xmlns="urn:jboss:module:1.1" name="org.jboss.as.web">
                                    <properties>
                                        <property name="jboss.api" value="private"/>
                                    </properties>
                                  .
                                  .
                                </module>
                                
                                

                                 

                                 

                                Also do not include the "jboss.api"  private property in your customer modules like "nu.xom", "net.sourceforge.nekohtml".

                                 

                                14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("nu.xom:main") which may be changed or removed in future versions without notice.
                                14:31:37,606 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("nu.xom:main") which may be changed or removed in future versions without notice.
                                
                                
                                • 13. Re: Re: Re: Jboss application not working in cluster in standalone mode.
                                  Abhishek Sharma Newbie

                                  Still I see the below even after starting my second JBoss Instance :

                                   

                                  16:59:14,623 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [2b69ddee-66ec-11e3-a79c-5c260a4f8f17]) started

                                  16:59:14,633 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

                                  16:59:14,643 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.queue.testQueue

                                  16:59:14,673 INFO  [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/queue/test

                                  16:59:14,683 INFO  [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

                                  16:59:14,683 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

                                  16:59:14,693 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory

                                  16:59:14,703 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.topic.testTopic

                                  16:59:14,713 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-5) JBAS010406: Registered connection factory java:/JmsXA

                                  16:59:14,723 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-5) HornetQ resource adaptor started

                                  16:59:14,723 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-5) IJ020002: Deployed: file://RaActivatorhornetq-ra

                                  16:59:14,733 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

                                  16:59:14,793 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/topic/test

                                  16:59:14,793 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test

                                  16:59:14,823 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "glog-ear.ear"

                                  16:59:14,823 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "ClusterWebApp.war"

                                  16:59:16,907 INFO  [stdout] (pool-13-thread-1)

                                  16:59:16,908 INFO  [stdout] (pool-13-thread-1) -------------------------------------------------------------------

                                  16:59:16,909 INFO  [stdout] (pool-13-thread-1) GMS: address=dell-pc/web, cluster=web, physical address=192.168.0.118:55200

                                  16:59:16,911 INFO  [stdout] (pool-13-thread-1) -------------------------------------------------------------------

                                   

                                   

                                  16:59:19,855 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                                  16:59:19,962 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                                  16:59:20,070 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000078: Starting JGroups Channel

                                  16:59:20,119 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000094: Received new cluster view: [dell-pc/web|0] [dell-pc/web]

                                   

                                   

                                  Also Jay after starting my second JBoss Instance I see the following errors in second JBoss instance :

                                   

                                  16:59:25,197 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "ClusterWebApp.war"

                                  16:59:25,207 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "glog-ear.ear"

                                  16:59:27,251 INFO  [stdout] (pool-9-thread-1)

                                  16:59:27,261 INFO  [stdout] (pool-9-thread-1) -------------------------------------------------------------------

                                  16:59:27,261 INFO  [stdout] (pool-9-thread-1) GMS: address=dell-pc/web, cluster=web, physical address=192.168.0.118:55201

                                  16:59:27,261 INFO  [stdout] (pool-9-thread-1) -------------------------------------------------------------------

                                   

                                   

                                  16:59:28,033 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=2b69ddee-66ec-11e3-a79c-5c260a4f8f17

                                  16:59:28,403 ERROR [org.jboss.msc.service.fail] (pool-9-thread-1) MSC00001: Failed to start service jboss.jgroups.channel.web: org.jboss.msc.service.StartException in service jboss.jgroups.channel.web: java.lang.IllegalStateException: JBAS010272: A node named dell-pc already exists in this cluster.  Perhaps there is already a server running on this host?  If so, restart this server with a unique node name, via -Djboss.node.name=<node-name>

                                    at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:62) [jboss-as-clustering-common-7.1.1.Final.jar:7.1.1.Final]

                                    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]

                                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]

                                    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]

                                  Caused by: java.lang.IllegalStateException: JBAS010272: A node named dell-pc already exists in this cluster.  Perhaps there is already a server running on this host?  If so, restart this server with a unique node name, via -Djboss.node.name=<node-name>

                                    at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:53) [jboss-as-clustering-jgroups-7.1.1.Final.jar:7.1.1.Final]

                                    at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:59) [jboss-as-clustering-common-7.1.1.Final.jar:7.1.1.Final]

                                    ... 3 more

                                   

                                   

                                  16:59:29,141 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=2b69ddee-66ec-11e3-a79c-5c260a4f8f17

                                  16:59:33,049 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=2b69ddee-66ec-11e3-a79c-5c260a4f8f17

                                  16:59:33,159 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-api.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,159 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,159 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr173_1.0_api.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,159 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb1-impl.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/lib/jaxb-impl-2.1.10.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "business-1.0.0.jar"

                                  16:59:33,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "service-1.0.0.jar"

                                  16:59:33,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "integration_transmitter-1.0.0.jar"

                                  16:59:33,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "ui-1.0.0.war"

                                  16:59:33,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "integration_receiver-1.0.0.jar"

                                  16:59:33,169 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "persistence-1.0.0.jar"

                                  16:59:33,209 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/hibernate-commons-annotations-3.3.0.ga.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,209 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/hibernate-3.2.1.ga.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,219 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/ehcache-1.6.0.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,229 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/asm-attrs-1.5.3.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,229 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/antlr-2.7.6.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,239 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/cglib-2.1_3.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,239 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/asm-1.5.3.jar in "/D:/Softwares/Abhi/jboss-as-7.1.1.Final/bin/content/glog-ear.ear/persistence-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.

                                  16:59:33,279 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'

                                  16:59:33,279 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'

                                  16:59:33,534 INFO  [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for LogitDatasourceV2

                                  16:59:33,755 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

                                  16:59:33,755 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

                                  16:59:33,755 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.xml.bind:main") which may be changed or removed in future versions without notice.

                                  16:59:33,765 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("com.sun.xml.bind:main") which may be changed or removed in future versions without notice.

                                  16:59:33,765 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("net.sourceforge.nekohtml:main") which may be changed or removed in future versions without notice.

                                  16:59:33,765 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("net.sourceforge.nekohtml:main") which may be changed or removed in future versions without notice.

                                  16:59:33,765 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("nu.xom:main") which may be changed or removed in future versions without notice.

                                  16:59:33,775 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("nu.xom:main") which may be changed or removed in future versions without notice.

                                  16:59:33,775 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.

                                  16:59:33,775 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.

                                  16:59:33,785 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.log4j:main") which may be changed or removed in future versions without notice.

                                  16:59:33,785 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.apache.log4j:main") which may be changed or removed in future versions without notice.

                                  16:59:33,785 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice.

                                  16:59:33,785 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice.

                                  16:59:33,785 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice.

                                  16:59:33,785 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice.

                                  16:59:33,795 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.as.web:main") which may be changed or removed in future versions without notice.

                                  16:59:33,795 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.as.web:main") which may be changed or removed in future versions without notice.

                                  16:59:33,795 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.osgi.framework:main") which may be changed or removed in future versions without notice.

                                  16:59:33,795 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.glog-ear.ear" is using a private module ("org.jboss.osgi.framework:main") which may be changed or removed in future versions without notice.

                                  16:59:33,795 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment glog-ear.ear

                                  16:59:33,815 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment integration_transmitter-1.0.0.jar

                                  16:59:33,815 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment service-1.0.0.jar

                                  16:59:33,815 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016002: Processing weld deployment integration_receiver-1.0.0.jar

                                  16:59:33,965 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment business-1.0.0.jar

                                  16:59:33,965 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment ui-1.0.0.war

                                  16:59:33,975 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named Authenticator in deployment unit subdeployment "business-1.0.0.jar" of deployment "glog-ear.ear" are as follows:

                                   

                                   

                                  Can u please help me on this

                                  • 14. Re: Re: Re: Re: Jboss application not working in cluster in standalone mode.
                                    Jay SenSharma Master

                                    When you want to run multiple JBoss instances as part of a cluster then every jboss should havce a unique node name which can be defined using the system property "jboss.node.name":

                                     

                                    Caused by: java.lang.IllegalStateException: JBAS010272: A node named dell-pc already exists in this cluster.  Perhaps there is already a server running on this host?  If so, restart this server with a unique node name, via -Djboss.node.name=<node-name>
                                    

                                     

                                     

                                    So you should start your JBoss nodes using the following system property:

                                     

                                    ./standalone.sh -c standalone-ha.xml -Djboss.node.name=NodeB -b YOUR_IPAddress
                                    ./standalone.sh -c standalone-ha.xml -Djboss.node.name=NodeC -b YOUR_Another_IPAddress
                                    
                                    1 2 3 Previous Next