[jboss-user] [Clustering/JBoss] - Re: Clustering JBoss 4.0.5, not working, stuck

[egandt]

I also tried adding java.naming.provider.url=172.19.2.10:1100:172.19.2.11:1100
to the all/conf/jndi.properties file, which force the a set of nodes.  This causes the first member to be brought up to throw exceptions, saying it can not contact the second member (which is understandable), but the second member (while not throwing any exceptions), also does not find the first cluster member:


Example of the second server starting up:
-------------------------------------------------------
  | GMS: address is oraclelinuxoracle11clusterA:1453 (additional data: 16 bytes)
  | -------------------------------------------------------
  | 22:15:41,835 INFO  [DefaultPartition] Number of cluster members: 1
  | 22:15:41,846 INFO  [DefaultPartition] Other members: 0
  | 22:15:41,847 INFO  [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
  | 22:15:41,872 INFO  [DefaultPartition] State could not be retrieved (we are the first member in group)
  | 22:15:42,578 INFO  [DefaultPartition] New cluster view for partition DefaultPartition (id: 0, delta: 0) : [172.19.2.10:1099]
  | 22:15:42,642 INFO  [DefaultPartition] I am (172.19.2.10:1099) received membershipChanged event:
  | 22:15:42,645 INFO  [DefaultPartition] Dead members: 0 ([])
  | 22:15:42,645 INFO  [DefaultPartition] New Members : 0 ([])
  | 22:15:42,646 INFO  [DefaultPartition] All Members : 1 ([172.19.2.10:1099])
  | 22:15:42,874 INFO  [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/172.19.2.10
  | 22:15:43,118 INFO  [DetachedHANamingService$AutomaticDiscovery] Listening on /172.19.2.10:1102, group=230.0.0.4, HA-JNDI address=172.19.2.10:1100
  | 22:15:50,536 INFO  [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3000000000000200000000000000E8000102000000000C3137322E31392E322E3130000DC80000000000114A426F73732F4E616D696E672F726F6F74000000000000050000000000000008000000004A414300000000010000001C000000000001000100000001050100010001010900000001050100010000002100000060000000000000000100000000000000240000001E0000007E00000000000000010000000C3137322E31392E322E3130000DC9004000000000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
  | 22:15:51,522 INFO  [CorbaTransactionService] TransactionFactory: [IOR:000000000000003049444C3A6F72672F6A626F73732F746D2F69696F702F5472616E73616374696F6E466163746F72794578743A312E30000000000200000000000000E8000102000000000C3137322E31392E322E3130000DC80000000000144A426F73732F5472616E73616374696F6E732F46000000050000000000000008000000004A414300000000010000001C000000000001000100000001050100010001010900000001050100010000002100000060000000000000000100000000000000240000001E0000007E00000000000000010000000C3137322E31392E322E3130000DC9004000000000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
  | 22:15:54,043 INFO  [Embedded] Catalina naming disabled
  | 22:15:54,204 INFO  [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
  | 22:15:54,215 INFO  [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
  | 22:15:56,100 INFO  [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-172.19.2.10-8080
  | 22:15:56,160 INFO  [Catalina] Initialization processed in 1940 ms
  | 


Notice it did not find the primary member 172.19.2.11 in this case, even though it is already started.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161783#4161783

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161783