1 2 Previous Next 28 Replies Latest reply on Dec 9, 2014 12:31 AM by Abhishek Sharma

    Getting WARN message in logs with hornetq in Jboss

    Abhishek Sharma Newbie

      I am really concerned about the following error. Please some one pick this up and suggest me how to overcome on this.

       

      19:35:27,946 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

      19:35:28,742 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

      19:35:32,962 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

      19:35:33,752 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

      19:35:38,032 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

      19:35:39,435 INFO  [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011942: Stopping OSGi Framework

        • 1. Re: Getting WARN message in logs with hornetq in Jboss
          Justin Bertram Master

          The log message is pretty unambiguous.

           

          At any point did you copy the configuration of one node to the other that might have included the HornetQ journal?  If so, you should delete the journal from one of the nodes and restart so that the nodeID can be recreated.

          • 2. Re: Getting WARN message in logs with hornetq in Jboss
            Abhishek Sharma Newbie

            Thanks Justin for your swift response.

             

            Yes, I have worked on standalone-ha.xml on NODE 1 and once i concluded that everything was fine I have copied the same to NODE 2 and then started both the JBoss which resulted in the WARN message.

             

            SO, Please suggest me how to delete the journal from one of the nodes.

            • 3. Re: Getting WARN message in logs with hornetq in Jboss
              Justin Bertram Master

              For JBoss AS7 and Wildfly standalone mode the HornetQ journal is stored in the <JBOSS_HOME>/standalone/data directory.  I think it would be safe to remove that whole directory.

              • 4. Re: Getting WARN message in logs with hornetq in Jboss
                Abhishek Sharma Newbie

                So I would prefer removing that folder in NODE 2 keeping the same in NODE 1. It works ?

                • 5. Re: Getting WARN message in logs with hornetq in Jboss
                  Justin Bertram Master

                  So I would prefer removing that folder in NODE 2 keeping the same in NODE 1. It works ?

                  I'm a bit confused.  Are you asking me if "it works"?

                   

                  To clarify, previously I said, "...you should delete the journal from one of the nodes and restart so that the nodeID can be recreated."

                  • 6. Re: Getting WARN message in logs with hornetq in Jboss
                    Abhishek Sharma Newbie

                    Sorry Justin. I got you wrong and deleted the whole data directory.

                    So now I am in the path D:\Softwares\Abhi\jboss-as-7.1.1.Final\standalone\data\messagingjournal

                    I see following files in that :

                    hornetq-data-1.hq

                    hornetq-data-2.hq

                    server.lock

                     

                    Which one do you want me to delete

                    (Or)

                    Do you want me to delete the whole messagingjournal folder.

                    Please suggest

                    • 7. Re: Getting WARN message in logs with hornetq in Jboss
                      Justin Bertram Master

                      I think it's fine that you removed the whole data directory.  You didn't get me wrong and I'm not sure why you think that.  As I said before, "For JBoss AS7 and Wildfly standalone mode the HornetQ journal is stored in the <JBOSS_HOME>/standalone/data directory.  I think it would be safe to remove that whole directory."

                      • 8. Re: Getting WARN message in logs with hornetq in Jboss
                        Abhishek Sharma Newbie

                        No It dint work Justin. As I could see continuous error following in my logs so I restored the same and now I see the old error again.

                         

                        21:21:29,211 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

                        • 9. Re: Getting WARN message in logs with hornetq in Jboss
                          Justin Bertram Master

                          What were the "continuous errors" you saw?

                           

                          If you stop the server, delete the data directory, and restart then nothing should break.  The data directory doesn't even exist when you unzip the server for the first time.  Everything in that directory should be auto-generated when the server starts up for the first time.  Of course, once everything is up and running you would want to be careful about deleting it since all your persistent message data would be in there, but at this point you're just trying to get your environment running so that shouldn't be an issue.

                          • 10. Re: Getting WARN message in logs with hornetq in Jboss
                            Abhishek Sharma Newbie

                            21:50:57,756 INFO  [stdout] (pool-10-thread-1)

                            21:50:57,756 INFO  [stdout] (pool-10-thread-1) -------------------------------------------------------------------

                            21:50:57,766 INFO  [stdout] (pool-10-thread-1) GMS: address=NodeB/web, cluster=web, physical address=192.168.0.118:55300

                            21:50:57,766 INFO  [stdout] (pool-10-thread-1) -------------------------------------------------------------------

                             

                             

                            21:51:00,636 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                            21:51:00,660 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.

                            21:51:00,764 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000078: Starting JGroups Channel

                            21:51:00,778 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000094: Received new cluster view: [NodeB/web|0] [NodeB/web]

                            21:51:00,784 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000079: Cache local address is NodeB/web, physical addresses are [192.168.0.118:55300]

                            21:51:00,804 INFO  [org.infinispan.factories.GlobalComponentRegistry] (pool-12-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL

                            21:51:00,807 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (pool-12-thread-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                            21:51:01,225 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-12-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

                            21:51:01,265 INFO  [org.jboss.as.clustering.infinispan] (pool-12-thread-1) JBAS010281: Started repl cache from web container

                            21:51:01,285 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (MSC service thread 1-8) JBAS010206: Number of cluster members: 1

                            21:51:01,457 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.

                            21:51:01,457 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

                            21:51:01,509 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-3) ISPN000031: MBeans were successfully registered to the platform mbean server.

                            21:51:01,549 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) JBAS010281: Started //default-host//ClusterWebApp cache from web container

                            21:51:01,569 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.

                            21:51:01,569 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.

                            21:51:01,821 INFO  [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /ClusterWebApp

                            21:51:04,596 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) 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.

                            21:51:04,605 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) 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.

                            21:51:04,608 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) 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.

                            21:51:04,603 ERROR [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 1096988878, [id: 0x4162b8ce, Dell-PC.router88c5e4.com/192.168.0.118:5545])) Failed to create session : HornetQException[errorCode=105 message=Unable to validate user: HORNETQ.CLUSTER.ADMIN.USER]

                              at org.hornetq.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:126) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.server.impl.HornetQServerImpl.createSession(HornetQServerImpl.java:807) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:187) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:85) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:508) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:556) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:517) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:533) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73) [hornetq-core-2.2.13.Final.jar:]

                              at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:534) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287) [netty-3.2.6.Final.jar:]

                              at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [hornetq-core-2.2.13.Final.jar:]

                              at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:367) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:100) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181) [netty-3.2.6.Final.jar:]

                              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]

                             

                             

                            21:51:04,622 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) 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.

                            21:51:04,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "business-1.0.0.jar"

                            21:51:04,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "integration_receiver-1.0.0.jar"

                            21:51:04,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "ui-1.0.0.war"

                            21:51:04,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "persistence-1.0.0.jar"

                            21:51:04,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "service-1.0.0.jar"

                            21:51:04,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "integration_transmitter-1.0.0.jar"

                            21:51:04,797 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

                            21:51:04,805 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

                            21:51:04,808 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

                            21:51:04,910 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

                            21:51:04,955 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

                            21:51:04,978 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

                            21:51:04,983 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.

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

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

                            21:51:05,525 ERROR [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 1096988878, [id: 0x4162b8ce, Dell-PC.router88c5e4.com/192.168.0.118:5545])) Failed to create session : HornetQException[errorCode=105 message=Unable to validate user: HORNETQ.CLUSTER.ADMIN.USER]

                              at org.hornetq.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:126) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.server.impl.HornetQServerImpl.createSession(HornetQServerImpl.java:807) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:187) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:85) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:508) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:556) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:517) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:533) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73) [hornetq-core-2.2.13.Final.jar:]

                              at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:534) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287) [netty-3.2.6.Final.jar:]

                              at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [hornetq-core-2.2.13.Final.jar:]

                              at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [hornetq-core-2.2.13.Final.jar:]

                              at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:367) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:100) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) [netty-3.2.6.Final.jar:]

                              at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181) [netty-3.2.6.Final.jar:]

                              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]

                             

                             

                            21:51:05,556 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for LogitDatasourceV2

                            21:51:05,556 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.lifecycle.web] (Incoming-1,null) JBAS010247: New cluster view for partition web (id: 1, delta: 1, merge: false) : [NodeB/web, NodeC/web]

                            21:51:05,656 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,null) ISPN000094: Received new cluster view: [NodeB/web|1] [NodeB/web, NodeC/web]

                            21:51:05,992 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:05,994 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:05,996 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:05,998 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,009 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,012 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,017 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,020 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,021 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,023 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,025 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,027 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,029 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,035 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,040 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,043 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,075 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,081 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,098 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,105 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.

                            21:51:06,109 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment glog-ear.ear

                            21:51:06,134 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment service-1.0.0.jar

                            21:51:06,175 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment integration_transmitter-1.0.0.jar

                            21:51:06,180 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment integration_receiver-1.0.0.jar

                            21:51:06,208 ERROR [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 1096988878, [id: 0x4162b8ce, Dell-PC.router88c5e4.com/192.168.0.118:5545])) Failed to create session : HornetQException[errorCode=105 message=Unable to validate user: HORNETQ.CLUSTER.ADMIN.USER]

                             

                             

                             

                             

                             

                            Same is the error in both the nodes. Where as I have removed only in  NODE 2.

                            • 11. Re: Getting WARN message in logs with hornetq in Jboss
                              Justin Bertram Master

                              Actually, those errors indicate to me that you're change was successful.  The HornetQ servers are now attempting to cluster together.  The problem now is that you haven't set the <cluster-password> to a non-default value that is the same on both nodes.

                              • 13. Re: Getting WARN message in logs with hornetq in Jboss
                                Justin Bertram Master

                                The <cluster-password> element is set in <hornetq-server> where all the HornetQ specific settings are.

                                • 14. Re: Getting WARN message in logs with hornetq in Jboss
                                  Abhishek Sharma Newbie

                                  Could you please help me with the path where I can locate HornetQ server

                                  1 2 Previous Next