-
15. Re: Re: Re: Re: Jboss application not working in cluster in standalone mode.
soranki Dec 3, 2014 8:20 AM (in response to jaysensharma)I have few questions
1) I have two Jboss running on the same box with same IP
2) I have standalone folders in both the boxes with the same name as "standalone"
3) as mentioned above -Djboss.node.name=NodeB what should be the node name given if the names of standalone are same.
-
16. Re: Re: Re: Re: Jboss application not working in cluster in standalone mode.
soranki Dec 3, 2014 8:33 AM (in response to jaysensharma)I see the below in Node 1
18:54:42,511 INFO [stdout] (pool-11-thread-1) -------------------------------------------------------------------
18:54:42,511 INFO [stdout] (pool-11-thread-1) GMS: address=NodeB/web, cluster=web, physical address=192.168.0.118:55200
18:54:42,511 INFO [stdout] (pool-11-thread-1) -------------------------------------------------------------------
18:54:44,820 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.
18:54:44,824 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:54:44,918 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000078: Starting JGroups Channel
18:54:45,003 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000094: Received new cluster view: [NodeB/web|0] [NodeB/web]
Here we can still see that [NodeB/web|0] (which should be [NodeB/web|1])
Command Given in NODE 1 :
standalone.bat -c standalone-ha.xml -b 192.168.0.118 -Djboss.node.name=NodeB
Where as I see the following error in NODE 2
D:\Softwares\Abhi\jboss-as-7.1.1.Final\standalone\deployments
19:01:28,284 ERROR [org.apache.coyote.ajp.AjpAprProtocol] (MSC service thread 1-2) Error initializing endpoint: java.lang.Exception: Socket bind failed: [730048] Only one usage of each socket address (protocol/network address/port) is normally permitted.
at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:584) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.ajp.AjpAprProtocol.init(AjpAprProtocol.java:176) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-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]
19:01:28,299 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Address already in use: bind /192.168.0.118:4447
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:109) [jboss-as-remoting-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]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_45]
at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135) [xnio-api-3.0.3.GA.jar:3.0.3.GA]
at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209) [jboss-remoting-3.2.3.GA.jar:3.2.3.GA]
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101) [jboss-as-remoting-7.1.1.Final.jar:7.1.1.Final]
... 5 more
19:01:28,293 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind /127.0.0.1:9999
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:109) [jboss-as-remoting-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]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_45]
at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135) [xnio-api-3.0.3.GA.jar:3.0.3.GA]
at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209) [jboss-remoting-3.2.3.GA.jar:3.2.3.GA]
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101) [jboss-as-remoting-7.1.1.Final.jar:7.1.1.Final]
... 5 more
19:01:28,291 ERROR [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) Error initializing endpoint: java.lang.Exception: Socket bind failed: [730048] Only one usage of each socket address (protocol/network address/port) is normally permitted.
at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:584) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-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]
19:01:28,378 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
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]
Caused by: LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [730048] Only one usage of each socket address (protocol/network address/port) is normally permitted.
at org.apache.catalina.connector.Connector.init(Connector.java:985)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
... 5 more
19:01:28,371 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=D:\Softwares\Abhi\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=D:\Softwares\Abhi\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=D:\Softwares\Abhi\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=D:\Softwares\Abhi\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
19:01:28,392 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) Waiting to obtain live lock
19:01:28,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment ClusterWebApp.war
19:01:28,399 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment glog-ear.ear
19:01:28,344 INFO [org.jboss.as.jacorb] (MSC service thread 1-3) JBAS016330: CORBA ORB Service started
19:01:28,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:210) [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]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124) [rt.jar:1.6.0_45]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_45]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:145)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:177) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
19:01:28,308 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.web.connector.ajp: org.jboss.msc.service.StartException in service jboss.web.connector.ajp: JBAS018007: Error starting web connector
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
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]
Caused by: LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [730048] Only one usage of each socket address (protocol/network address/port) is normally permitted.
at org.apache.catalina.connector.Connector.init(Connector.java:985)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
... 5 more
19:01:28,410 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-7) Initializing mod_cluster 1.2.0.Final
19:01:28,431 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-8) Using NIO Journal
19:01:28,469 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-7) Listening to proxy advertisements on 224.0.1.105:23364
19:01:28,461 WARN [jacorb.orb.iiop] (MSC service thread 1-3) could not create server socket port: 3528 host: /127.0.0.1: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_45]
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_45]
at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_45]
at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_45]
at org.jacorb.orb.factory.DefaultServerSocketFactory.createServerSocket(DefaultServerSocketFactory.java:49) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:572) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153) [jboss-as-jacorb-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]
19:01:28,488 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.jacorb.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.jacorb.poa-service.rootpoa: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use: JVM_Bind
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:155)
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]
Caused by: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use: JVM_Bind
at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:580)
at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417)
at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163)
at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125)
at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74)
at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102)
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036)
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307)
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153)
... 5 more
19:01:28,749 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-8) Waiting to obtain live lock
19:01:28,749 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-8) Live Server Obtained live lock
19:01:29,090 WARN [org.hornetq.core.server.cluster.impl.BroadcastGroupImpl] (MSC service thread 1-8) local-bind-address specified for broadcast group but no local-bind-port specified so socket will NOT be bound to a local address/port
19:01:29,150 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-8) Started Netty Acceptor version 3.2.5.Final-a96d88c Dell-PC.router88c5e4.com:5445 for CORE protocol
19:01:29,150 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-8) Started Netty Acceptor version 3.2.5.Final-a96d88c Dell-PC.router88c5e4.com:5455 for CORE protocol
19:01:29,150 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) Server is now live
19:01:29,150 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [2b69ddee-66ec-11e3-a79c-5c260a4f8f17]) started
19:01:29,160 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) trying to deploy queue jms.queue.testQueue
19:01:29,160 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/queue/test
19:01:29,160 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test
19:01:29,180 INFO [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
19:01:29,180 INFO [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
19:01:29,180 INFO [org.jboss.as.messaging] (MSC service thread 1-6) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
19:01:29,180 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.topic.testTopic
19:01:29,220 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
19:01:29,230 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
19:01:29,230 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
19:01:29,230 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-8) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
19:01:29,260 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/topic/test
19:01:29,260 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test
19:01:29,890 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.connector.ajp: org.jboss.msc.service.StartException in service jboss.web.connector.ajp: JBAS018007: Error starting web connector
service jboss.jacorb.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.jacorb.poa-service.rootpoa: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use: JVM_Bind
service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Address already in use: bind /127.0.0.1:9999
service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Address already in use: bind /192.168.0.118:4447
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
19:01:29,920 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "ClusterWebApp.war"
19:01:29,920 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "glog-ear.ear"
19:01:30,878 INFO [stdout] (pool-13-thread-1)
19:01:30,878 INFO [stdout] (pool-13-thread-1) -------------------------------------------------------------------
19:01:30,878 INFO [stdout] (pool-13-thread-1) GMS: address=NodeC/web, cluster=web, physical address=192.168.0.118:55200
19:01:30,878 INFO [stdout] (pool-13-thread-1) -------------------------------------------------------------------
19:01:33,429 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.
19:01:33,429 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
19:01:33,578 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000078: Starting JGroups Channel
19:01:33,594 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000094: Received new cluster view: [NodeC/web|0] [NodeC/web]
19:01:33,596 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-1) ISPN000079: Cache local address is NodeC/web, physical addresses are [192.168.0.118:55200]
-
17. Re: Re: Re: Re: Re: Jboss application not working in cluster in standalone mode.
jaysensharma Dec 3, 2014 8:56 AM (in response to soranki)If you are running multiple instances in the same physical machine then you must set the port-offset while starting your JBoss in order to avoid port conflicts. Example:
See:
JBAS017112: Address already in use: bind /127.0.0.1:9999
Example:
./standalone.sh -c standalone-ha.xml -Djboss.node.name=NodeA -b YOUR_IPAddress -Djboss.socket.binding.port-offset=100 ./standalone.sh -c standalone-ha.xml -Djboss.node.name=NodeB -b YOUR_IPAddress -Djboss.socket.binding.port-offset=200 ./standalone.sh -c standalone-ha.xml -Djboss.node.name=NodeC -b YOUR_Another_IPAddress -Djboss.socket.binding.port-offset=300
Your queries:
============
1) I have two Jboss running on the same box with same IP
>> Use -Djboss.socket.binding.port-offset to avoid port conflicts. Or run your different JBoss instances on diffrernt IP Addresses if you have multiple IP Addresses (NIC for the machine)
2) I have standalone folders in both the boxes with the same name as "standalone"
>> That's fine (as long as they are in different boxes)
3) as mentioned above -Djboss.node.name=NodeB what should be the node name given if the names of standalone are same
>> Any unique String, But it should be unique among all the cluster members.
-
18. Re: Re: Re: Re: Re: Jboss application not working in cluster in standalone mode.
soranki Dec 3, 2014 9:21 AM (in response to jaysensharma)Now i see the following on my NODE II. Can I now assume that now I am in clustered mode ?
19:35:08,725 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-5) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
19:35:08,795 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
19:35:08,795 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test
19:35:08,795 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.queue.testQueue
19:35:08,805 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/queue/test
19:35:08,815 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test
19:35:08,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "glog-ear.ear"
19:35:08,901 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "ClusterWebApp.war"
19:35:09,894 INFO [stdout] (pool-11-thread-1)
19:35:09,908 INFO [stdout] (pool-11-thread-1) -------------------------------------------------------------------
19:35:09,916 INFO [stdout] (pool-11-thread-1) GMS: address=NodeC/web, cluster=web, physical address=192.168.0.118:55400
19:35:09,917 INFO [stdout] (pool-11-thread-1) -------------------------------------------------------------------
19:35:10,384 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.
19:35:10,393 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.
19:35:10,467 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000078: Starting JGroups Channel
19:35:10,467 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000094: Received new cluster view: [NodeB/web|1] [NodeB/web, NodeC/web]
19:35:10,477 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000079: Cache local address is NodeC/web, physical addresses are [192.168.0.118:55400]
But, still I find the following logs binding at the end
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
-
19. Re: Jboss application not working in cluster in standalone mode.
jaysensharma Dec 3, 2014 9:38 AM (in response to soranki)the latest WARN is specific to HornetQ , So please open a separate thread from hornetQ perspective to get more accurate visibility to this issue.
-
20. Re: Jboss application not working in cluster in standalone mode.
soranki Dec 3, 2014 9:50 AM (in response to jaysensharma)Sure Jay, But also please have a look at below error where I am not able to access my application but the JBoss instances are up and running.
19:35:24,141 INFO [org.jboss.as.clustering.infinispan] (pool-12-thread-1) JBAS010282: Stopped repl cache from web container
19:35:24,171 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-10-thread-1) ISPN000082: Stopping the RpcDispatcher
19:35:24,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment ui-1.0.0.war in 379ms
19:35:24,383 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment glog-ear.ear in 429ms
19:35:24,383 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.mysqldomain (missing) dependents: [service jboss.web.deployment.default-host./OceanView.realm]
19:35:24,393 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
19:35:24,393 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.deployment.default-host./OceanView.realmjboss.security.security-domain.mysqldomainMissing[jboss.web.deployment.default-host./OceanView.realmjboss.security.security-domain.mysqldomain]"]}}}
Also please let me know that whether I am in clustered mode or not.
-
21. Re: Re: Jboss application not working in cluster in standalone mode.
jaysensharma Dec 3, 2014 10:13 AM (in response to soranki)Abhishek,
This is because in your update https://developer.jboss.org/message/912211#912211 you posted your standalone-ha.xml file where i do not see any "security-domain" configured with name "mysqldomain", But your application seems to be having some jboss-web.xml or jboss-ejb3.xml or using annotation it might be pointing to security-domain with name "mysqldomain" which is missing in your standalone-ha.xml hence JBoss is complaining.
JBAS014775: New missing/unsatisfied dependencies: service jboss.security.security-domain.mysqldomain (missing) dependents: [service jboss.web.deployment.default-host./OceanView.realm]
-
22. Re: Re: Jboss application not working in cluster in standalone mode.
soranki Dec 3, 2014 10:19 AM (in response to jaysensharma)So How to fix this and what are the configurations that I have to change. Please suggest. Also please let me know that whether I am in clustered mode or not.
-
23. Re: Re: Re: Jboss application not working in cluster in standalone mode.
jaysensharma Dec 3, 2014 10:42 AM (in response to soranki)Abhishek,
Regarding your query "So How to fix this and what are the configurations that I have to change."
>>>> Please refer to [1] to know about how to configure security-domain in JBoss AS7
Regarding your query "please let me know that whether I am in clustered mode or not."
>>>> In your log output Re: Re: Re: Re: Re: Jboss application not working in cluster in standalone mode. we see the following, Which indicates that your JBoss NodeB and NodeC have joined the cluster and are in cluster mode.
19:35:10,467 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-12-thread-1) ISPN000094: Received new cluster view: [NodeB/web|1] [NodeB/web, NodeC/web]
-
24. Re: Re: Re: Jboss application not working in cluster in standalone mode.
soranki Dec 3, 2014 11:02 AM (in response to jaysensharma)The following is the standalone.xml. So where do I have to change the configuration acording to the link provide by you. Please suggest.
</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="mysqldomain" cache-type="default">
<authentication>
<login-module code="Database" flag="required">
<module-option name="dsJndiName" value="java:jboss/datasources/Logit-DS"/>
<module-option name="principalsQuery" value="select UAC_PASSWORD from USER_ACCOUNT where UAC_NAME=?"/>
<module-option name="rolesQuery" value="select URO_ROLENAME,'Roles' from USER_ROLE where URO_ID in (select uu.URO_ID from USER_ACCOUNT ua join useraccount_userrole uu on ua.id=uu.UAC_ID where ua.UAC_NAME=?)"/>
<module-option name="hashAlgorithm" value="MD5"/>
<module-option name="hashEncoding" value="BASE64"/>
<module-option name="hashStorePassword" value="true"/>
</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>
-
25. Re: Jboss application not working in cluster in standalone mode.
soranki Dec 5, 2014 4:25 AM (in response to soranki)I am really finding it difficult to match the configuration sent in the document with mine. So please help me out how to over come the above stated issue.
-
26. Re: Re: Jboss application not working in cluster in standalone mode.
jaysensharma Dec 5, 2014 4:42 AM (in response to soranki)Abhishek,
As mentioned earlier that this thread was specifically for running jboss cluster in standalone mode. As per the observation mentioned in Re: Re: Re: Jboss application not working in cluster in standalone mode. I see that your cluster issue is resolved.
The new query which you have is very specific to security-domain configuration. In order to maintain a good forum and attract collaborators attention from the correct set of expertise and focus it is appreciated to open separate threads for different un related queries.
Still if you find that your last query should be discussed on this thread only, then please tell us what issue (Error/Exception) are u seeing with the current security-domain?
-
27. Re: Jboss application not working in cluster in standalone mode.
soranki Dec 5, 2014 4:48 AM (in response to jaysensharma)Sure Jay. I am opening a new thread regarding the issue I am facing and I would really appreciate if the issue is resolved.
-
28. Re: Jboss application not working in cluster in standalone mode.
soranki Dec 5, 2014 4:50 AM (in response to soranki)And I am really thankful to you throughout the journey in achieving the Jboss clustering.
-
29. Re: Jboss application not working in cluster in standalone mode.
soranki Dec 5, 2014 5:06 AM (in response to soranki)I have created a thread and below is the subject line given to that.
Facing major issue in setting up security-domain configuration