Re: [jboss-as7-dev] TCPPING in AS7

Hi Bill The configuration is valid. I tried it out on my local machine. I set up two AS 7.1.1. instances, configured as you describe but using a different set of IPv4 addresses (I used 192.168.0.103, 192.168.0.104 and used "iptables -F" to let multicast messages through). Because clustering services are installed on-demand, they need some event to to start them, so I also deployed a small clustered web application. When I start both instances, no channels are started, as expected: $ ./standalone.sh --server-config standalone-ha.xml -Djboss.bind.address=192.168.0.103 -Djboss.bind.address.management=192.168.0.103 -Djboss.node.name=A $ ./standalone.sh --server-config standalone-ha.xml -Djboss.bind.address=192.168.0.104 -Djboss.bind.address.management=192.168.0.104 -Djboss.node.name=B When I deployed the clustered web app on each application server instance to trigger Infinispan web cache container and JGroups tcp channel startup, I saw for example, on the first host A: 18:58:41,086 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-8) JBAS010281: Started //default-host//my-clustered-webapp cache from web container 18:58:41,096 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. 18:58:41,099 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. 18:58:41,220 INFO [org.jboss.web] (MSC service thread 1-8) JBAS018210: Registering web context: /my-clustered-webapp 18:58:41,230 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "my-clustered-webapp.war" 18:58:41,333 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.0.103:9990 18:58:41,334 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" started in 6719ms - Started 175 of 305 services (129 services are passive or on-demand) 18:58:50,673 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) : [A/web, B/web] 18:58:50,687 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,null) ISPN000094: Received new cluster view: [A/web|1] [A/web, B/web] So, it seems as though things work as expected. I also tried to achieve the same effect by not deploying the web app and setting the attribute start="EAGER" on a clustered Infinispan cache (in this case, cache "repl" in the "web" cache container) to force them to start as active services. When the application servers were started this time, same result: clustering between the two nodes was visible. If I instead set the start="EAGER" attribute on a cache container, however, the channels do not get started automatically and I need to deploy a web app as before to trigger starting of the transport. So, are you using start=EAGER to start the cache instances, or deploying an app to trigger them? The organization of Infinispan services has changed a lot since 7.1.0. In particular, a cache container needs to specify the <transport/> element in order for a transport to be used. Richard On 03/14/2012 05:47 PM, Brian Stansberry wrote: