[quote=windwalker78]
These are the logs of the DAS and one of the instances after fresh start of
the domain, cluster and issuing the get-health command:
server_das.log [1]
http://niti95.com/uploads/server_das.log
server_inst1.log [2]
http://niti95.com/uploads/server_inst1.log
[/quote]
My email still hasn't shown up here, but maybe I can simplify things a bit. I
didn't see the log URLs before, and looking at them now I see that GMS (the
system that supports HA and the get-health command) is working. At least in
the inst1 log, I see that it knows about inst2 from this entry (look for
ShoalLogger for these):
[#|2011-04-20T22:46:49.581+0300|INFO|glassfish3.1|ShoalLogger|_ThreadID=12;_ThreadName=Thread-1;|GMS1092:
GMS View Change Received for group: cluster1 : Members in view for
JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: inst1, MemberType: CORE, Address:
192.168.3.203:9143:228.9.151.111:25336:cluster1:inst1
2: MemberId: inst2, MemberType: CORE, Address:
192.168.3.204:9195:228.9.151.111:25336:cluster1:inst2
I don't see the DAS there, which would show up as member id "server." Because
the timestamps are different in the two logs, I can't compare the inst1 log
to what I see in the DAS. If those logs are from the same run, my guess is
that the clocks on these two systems aren't in sync, and so the DAS is
getting messages from the instances but they can't be processed. In the DAS
log after the "GMS1062: GroupStart" message, you should start seeing messages
like "GMS1024: Adding Join member: inst1".
Can you check the times on the two machines and see if they're way off? After
that, you can try increasing the log level for ShoalLogger to see what's
going on. But multicast is definitely working on your machines, so you can
skip debugging that part.
Cheers,
Bobby
[1]
http://niti95.com/uploads/server_das.log
[2]
http://niti95.com/uploads/server_inst1.log
--
[Message sent by forum member 'bbissett']
View Post: http://forums.java.net/node/793566