I've tried to reproduce this behavior manually. I've got my hands on two
machines that have glassfish installed and configured the same way. I've
manually changed the GMS address and port on one of the clusters. Then I've
restarted the clusters a couple of times. I couldn't make the other cluster
stop (or start). When stopping them, i would get a normal log. However, when
starting one of them, i would get the following, expected log:
[#|2012-11-28T00:51:16.879-0800|INFO|glassfish3.1.1|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|GMS1092:
GMS View Change Received for group: POD_Processing_Cl01 : Members in view for
JOINED_AND_READY_EVENT(before change analysis) are : 1: MemberId:
POD_Processing_Cl01_ins01, MemberType: CORE, Address:
10.220.20.118:9095:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins01
2: MemberId: POD_Processing_Cl01_ins01, MemberType: CORE, Address:
10.220.20.194:9137:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins01
3: MemberId: POD_Processing_Cl01_ins02, MemberType: CORE, Address:
10.220.20.118:9104:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins02
4: MemberId: POD_Processing_Cl01_ins02, MemberType: CORE, Address:
10.220.20.194:9106:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins02
5: MemberId: server, MemberType: SPECTATOR, Address:
10.220.20.194:9143:228.9.103.196:16084:POD_Processing_Cl01:server |#]
[#|2012-11-28T00:51:16.879-0800|INFO|glassfish3.1.1|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|GMS1016:
Analyzing new membership snapshot received as part of event:
JOINED_AND_READY_EVENT for member: POD_Processing_Cl01_ins01 of group:
POD_Processing_Cl01|#]
[#|2012-11-28T00:51:16.879-0800|INFO|glassfish3.1.1|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|GMS1025:
Adding Joined And Ready member: POD_Processing_Cl01_ins01 group:
POD_Processing_Cl01 StartupState: INSTANCE_STARTUP |#]
[#|2012-11-28T00:51:32.847-0800|INFO|glassfish3.1.1|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|GMS1092:
GMS View Change Received for group: POD_Processing_Cl01 : Members in view for
JOINED_AND_READY_EVENT(before change analysis) are : 1: MemberId:
POD_Processing_Cl01_ins01, MemberType: CORE, Address:
10.220.20.118:9095:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins01
2: MemberId: POD_Processing_Cl01_ins01, MemberType: CORE, Address:
10.220.20.194:9137:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins01
3: MemberId: POD_Processing_Cl01_ins02, MemberType: CORE, Address:
10.220.20.118:9104:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins02
4: MemberId: POD_Processing_Cl01_ins02, MemberType: CORE, Address:
10.220.20.194:9106:228.9.103.196:16084:POD_Processing_Cl01:POD_Processing_Cl01_ins02
5: MemberId: server, MemberType: SPECTATOR, Address:
10.220.20.194:9143:228.9.103.196:16084:POD_Processing_Cl01:server |#]
[#|2012-11-28T00:51:32.847-0800|INFO|glassfish3.1.1|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|GMS1016:
Analyzing new membership snapshot received as part of event:
JOINED_AND_READY_EVENT for member: POD_Processing_Cl01_ins02 of group:
POD_Processing_Cl01|#]
[#|2012-11-28T00:51:32.847-0800|INFO|glassfish3.1.1|ShoalLogger|_ThreadID=18;_ThreadName=Thread-2;|GMS1025:
Adding Joined And Ready member: POD_Processing_Cl01_ins02 group:
POD_Processing_Cl01 StartupState: INSTANCE_STARTUP |#] Still, only one
cluster is up. Not both of them. Are there any other configurations that
could have been done in the first case, when both clusters came down? Thank
you for your time and patience.
--
[Message sent by forum member 'sebigavril']
View Post: http://forums.java.net/node/892700