[jboss-user] [Clustering/JBoss] - Re: Order of node start up works one way, but not the other

[PhilipWu]

Thanx for the quick reply:

1) I am using Jboss 4.0.5.GA installed with 1.2.0.GA jems installer, with ejb3-clustered configuration.

2) If I start node A and then node B, it is node B that gives that warning. I had switched log4j.xml to DEBUG level and I see no errors coming from node A. According to the logs, it appers at first that they can find each other and they are registered in a cluster. But soon afterwards node B is removed from the cluster probably because of the WARN message.

In the trace below node A = 192.168.1.100, node B = 192.168.1.105

Here's a larger trace of node B:

13:09:10,407 INFO  [FRAG2] frag_size=60000, overhead=0, new frag_size=60000
  | 13:09:10,516 INFO  [UDP] unicast sockets will use interface 192.168.1.105
  | 13:09:10,521 INFO  [UDP] socket information:
  | local_addr=localhost:32811, mcast_addr=228.1.2.4:45577, bind_addr=/192.168.1.105, ttl=2
  | sock: bound to 192.168.1.105:32811, receive buffer size=109568, send buffer size=109568
  | mcast_recv_sock: bound to 192.168.1.105:45577, send buffer size=109568, receive buffer size=109568
  | mcast_send_sock: bound to 192.168.1.105:32812, send buffer size=109568, receive buffer size=109568
  | 13:09:10,522 INFO  [STDOUT] 
  | -------------------------------------------------------
  | GMS: address is localhost:32811
  | -------------------------------------------------------
  | 13:09:12,815 INFO  [TreeCache] TreeCache local address is localhost:32811
  | 13:09:12,816 INFO  [TreeCache] viewAccepted(): [192.168.1.100:32771|1] [192.168.1.100:32771, localhost:32811]
  | 13:09:27,832 WARN  [ServiceController] Problem starting service jboss.cache:service=TomcatClusteringCache
  | org.jboss.cache.CacheException: Initial state transfer failed: Channel.getState() returned false
  |         at org.jboss.cache.TreeCache.fetchStateOnStartup(TreeCache.java:3191)
  |         at org.jboss.cache.TreeCache.startService(TreeCache.java:1429)
  | 

Here's some of the trace from node A:

2007-03-06 12:53:50,201 DEBUG [org.jgroups.protocols.pbcast.GMS] mbr=192.168.1.105:32811
  | 2007-03-06 12:53:50,201 DEBUG [org.jgroups.protocols.pbcast.CoordGmsImpl] mbr=192.168.1.105:32811
  | 2007-03-06 12:53:50,202 DEBUG [org.jgroups.protocols.pbcast.CoordGmsImpl] got digest=[localhost:32771: [5 : 6]
  | 2007-03-06 12:53:50,202 DEBUG [org.jgroups.protocols.pbcast.GMS] VID=1, current members=(localhost:32771), new_mbrs=(192.168.1.105:32811), old
  | _mbrs=(), suspected_mbrs=()
  | 2007-03-06 12:53:50,202 DEBUG [org.jgroups.protocols.pbcast.GMS] new view is [localhost:32771|1] [localhost:32771, 192.168.1.105:32811]
  | 2007-03-06 12:53:50,202 DEBUG [org.jgroups.protocols.pbcast.CoordGmsImpl] joined member 192.168.1.105:32811, view is [localhost:32771|1] [loca
  | lhost:32771, 192.168.1.105:32811]

3) No exceptions in Node A

Thanx,

Phil


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

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