Issue Details (XML | Word | Printable)

Key: GLASSFISH-18744
Type: Bug Bug
Status: Closed Closed
Resolution: Invalid
Priority: Major Major
Assignee: Amy Roh
Reporter: oversteer
Votes: 1
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
glassfish

Can't start-cluster on Windows 7 with enableJK set in domain.xml

Created: 21/May/12 12:54 PM   Updated: 04/Jan/13 08:19 PM   Resolved: 04/Jan/13 08:19 PM
Component/s: web_container
Affects Version/s: 3.1.2
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. XML File domain.xml (44 kB) 21/May/12 12:54 PM - oversteer

Environment:

Windows 7 JDK 1.7.0_04 (also tested on JDK 1.6.0_24)


Tags: cluster
Participants: Amy Roh and oversteer


 Description  « Hide

The HA admin guide does not, as far as I can see, make any reference to the
com.sun.enterprise.web.connector.enableJK jvm option although just about every
blog does. I'm assuming that it does need to be set to run mod_jk/glassfish.

When trying to run a load balanced application with mod_jk/glassfish and not
setting enableJK the behavior I observe is that (I'm using container security)
a j_security_check postback sets the Location response header (the next page
that the client will GET) to the Origin field from the response, instead of
the Referer field which is normally used. Net result is that you can't login.

I also notice that with stick_session=false I'm not seeing requests round robin'ed
between the two instances, but this is perhaps to be expected with enableJK not set.

This is how I can reproduce the problem:

Starting with the domain.xml shipped with Glassfish 3.1.2 I execute the following commands:
(note: this is not the full working config but it's all that's needed to cause the error)

asadmin>

enable-secure-admin
restart-domain
create-cluster c1
create-local-instance --cluster c1 i1
create-local-instance --cluster c1 i2
start-cluster c1
create-system-properties --target i1 AJP_PORT=8010
create-system-properties --target i2 AJP_PORT=8011
start-cluster

The cluster starts ok, then:

create-jvm-options --target c1 "-Dcom.sun.enterprise.web.connector.enableJK=\${AJP_PORT}"
stop-cluster
start-cluster

asadmin> start-cluster c1
remote failure: i1: Could not start instance i1 on node localhost-domain1 (local
host).

Command failed on node localhost-domain1 (localhost): Attempting to start i1....
Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost f
rom the GlassFish install location C:\glassfish-3.1.2:

bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
i2: Could not start instance i2 on node localhost-domain1 (localhost).

Command failed on node localhost-domain1 (localhost): Attempting to start i2....
Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost f
rom the GlassFish install location C:\glassfish-3.1.2:

bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2

The command start-instance failed for: i1 i2
Command start-cluster failed.
asadmin>

In the server log I see the following output which is generated specifically as
a result of the failing start-cluster command:

INFO: GMS1098: GMS:Announcing GroupStartup[INITIATED] for group: c1 members: i1,i2,
INFO: GMS1062: GroupStart for group: c1 State: INITIATED Starting Members: i1,i2,
INFO: Starting cluster c1
INFO: Executing start-instance on 2 instances using a thread pool of size 2: localhost-domain1:i1 localhost-domain1:i2
INFO: start-instance i1
INFO: start-instance i2
INFO: CLI801 Instance is already synchronized
INFO: CLI801 Instance is already synchronized
INFO: Attempting to start i1.... Please look at the server log for more details.....
INFO: Attempting to start i2.... Please look at the server log for more details.....
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i2 of group: c1
INFO: GMS1024: Adding Join member: i2 group: c1 StartupState: GROUP_STARTUP
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i1 of group: c1
WARNING: Could not start instance i2 on node localhost-domain1 (localhost).: Command ' C:\glassfish-3.1.2\glassfish\bin\asadmin.bat --_auxinput - --interactive=false start-local-instance --node localhost-domain1 --sync normal i2' failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i2.... Please look at the server log for more details.....: To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2
SEVERE: i2: Could not start instance i2 on node localhost-domain1 (localhost).
Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i2.... Please look at the server log for more details.....
To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2
WARNING: Could not start instance i1 on node localhost-domain1 (localhost).: Command ' C:\glassfish-3.1.2\glassfish\bin\asadmin.bat --_auxinput - --interactive=false start-local-instance --node localhost-domain1 --sync normal i1' failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i1.... Please look at the server log for more details.....: To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
SEVERE: i1: Could not start instance i1 on node localhost-domain1 (localhost).
Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i1.... Please look at the server log for more details.....
To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
INFO: GMS1024: Adding Join member: i1 group: c1 StartupState: GROUP_STARTUP
SEVERE: Connection refused: no further information
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: IN_DOUBT_EVENT for member: i2 of group: c1
INFO: GMS1007: Received FailureSuspectedEvent for member: i2 of group: c1
INFO: GMS1005: Sending FailureSuspectedSignals to registered Actions. member: i2 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: IN_DOUBT_EVENT for member: i1 of group: c1
INFO: GMS1007: Received FailureSuspectedEvent for member: i1 of group: c1
INFO: GMS1005: Sending FailureSuspectedSignals to registered Actions. member: i1 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for FAILURE_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: FAILURE_EVENT for member: i2 of group: c1
INFO: GMS1019: member: i2 of group: c1 has failed
INFO: GMS1003: Sending FailureNotificationSignals to registered Actions. member: i2 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for FAILURE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: FAILURE_EVENT for member: i1 of group: c1
INFO: GMS1019: member: i1 of group: c1 has failed
INFO: GMS1003: Sending FailureNotificationSignals to registered Actions. member: i1 ...



shreedhar_ganapathy made changes - 13/Dec/12 08:49 PM
Field Original Value New Value
Assignee shreedhar_ganapathy [ shreedhar_ganapathy ] amyroh [ amyroh ]
Description
The HA admin guide does not, as far as I can see, make any reference to the
com.sun.enterprise.web.connector.enableJK jvm option although just about every
blog does. I'm assuming that it does need to be set to run mod_jk/glassfish.

When trying to run a load balanced application with mod_jk/glassfish and not
setting enableJK the behavior I observe is that (I'm using container security)
a j_security_check postback sets the Location response header (the next page
that the client will GET) to the Origin field from the response, instead of
the Referer field which is normally used. Net result is that you can't login.

I also notice that with stick_session=false I'm not seeing requests round robin'ed
between the two instances, but this is perhaps to be expected with enableJK not set.

This is how I can reproduce the problem:

Starting with the domain.xml shipped with Glassfish 3.1.2 I execute the following commands:
(note: this is not the full working config but it's all that's needed to cause the error)

asadmin>

enable-secure-admin
restart-domain
create-cluster c1
create-local-instance --cluster c1 i1
create-local-instance --cluster c1 i2
start-cluster c1
create-system-properties --target i1 AJP_PORT=8010
create-system-properties --target i2 AJP_PORT=8011
start-cluster

The cluster starts ok, then:

create-jvm-options --target c1 "-Dcom.sun.enterprise.web.connector.enableJK=\${AJP_PORT}"
stop-cluster
start-cluster

asadmin> start-cluster c1
remote failure: i1: Could not start instance i1 on node localhost-domain1 (local
host).

Command failed on node localhost-domain1 (localhost): Attempting to start i1....
 Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost f
rom the GlassFish install location C:\glassfish-3.1.2:

 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
i2: Could not start instance i2 on node localhost-domain1 (localhost).

Command failed on node localhost-domain1 (localhost): Attempting to start i2....
 Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost f
rom the GlassFish install location C:\glassfish-3.1.2:

 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2

The command start-instance failed for: i1 i2
Command start-cluster failed.
asadmin>

In the server log I see the following output which is generated specifically as
a result of the failing start-cluster command:


INFO: GMS1098: GMS:Announcing GroupStartup[INITIATED] for group: c1 members: i1,i2,
INFO: GMS1062: GroupStart for group: c1 State: INITIATED Starting Members: i1,i2,
INFO: Starting cluster c1
INFO: Executing start-instance on 2 instances using a thread pool of size 2: localhost-domain1:i1 localhost-domain1:i2
INFO: start-instance i1
INFO: start-instance i2
INFO: CLI801 Instance is already synchronized
INFO: CLI801 Instance is already synchronized
INFO: Attempting to start i1.... Please look at the server log for more details.....
INFO: Attempting to start i2.... Please look at the server log for more details.....
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i2 of group: c1
INFO: GMS1024: Adding Join member: i2 group: c1 StartupState: GROUP_STARTUP
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i1 of group: c1
WARNING: Could not start instance i2 on node localhost-domain1 (localhost).: Command ' C:\glassfish-3.1.2\glassfish\bin\asadmin.bat --_auxinput - --interactive=false start-local-instance --node localhost-domain1 --sync normal i2' failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i2.... Please look at the server log for more details.....: To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2
SEVERE: i2: Could not start instance i2 on node localhost-domain1 (localhost).
Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i2.... Please look at the server log for more details.....
To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2
WARNING: Could not start instance i1 on node localhost-domain1 (localhost).: Command ' C:\glassfish-3.1.2\glassfish\bin\asadmin.bat --_auxinput - --interactive=false start-local-instance --node localhost-domain1 --sync normal i1' failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i1.... Please look at the server log for more details.....: To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
SEVERE: i1: Could not start instance i1 on node localhost-domain1 (localhost).
Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i1.... Please look at the server log for more details.....
To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
INFO: GMS1024: Adding Join member: i1 group: c1 StartupState: GROUP_STARTUP
SEVERE: Connection refused: no further information
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: IN_DOUBT_EVENT for member: i2 of group: c1
INFO: GMS1007: Received FailureSuspectedEvent for member: i2 of group: c1
INFO: GMS1005: Sending FailureSuspectedSignals to registered Actions. member: i2 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: IN_DOUBT_EVENT for member: i1 of group: c1
INFO: GMS1007: Received FailureSuspectedEvent for member: i1 of group: c1
INFO: GMS1005: Sending FailureSuspectedSignals to registered Actions. member: i1 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for FAILURE_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: FAILURE_EVENT for member: i2 of group: c1
INFO: GMS1019: member: i2 of group: c1 has failed
INFO: GMS1003: Sending FailureNotificationSignals to registered Actions. member: i2 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for FAILURE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: FAILURE_EVENT for member: i1 of group: c1
INFO: GMS1019: member: i1 of group: c1 has failed
INFO: GMS1003: Sending FailureNotificationSignals to registered Actions. member: i1 ...




The HA admin guide does not, as far as I can see, make any reference to the
com.sun.enterprise.web.connector.enableJK jvm option although just about every
blog does. I'm assuming that it does need to be set to run mod_jk/glassfish.

When trying to run a load balanced application with mod_jk/glassfish and not
setting enableJK the behavior I observe is that (I'm using container security)
a j_security_check postback sets the Location response header (the next page
that the client will GET) to the Origin field from the response, instead of
the Referer field which is normally used. Net result is that you can't login.

I also notice that with stick_session=false I'm not seeing requests round robin'ed
between the two instances, but this is perhaps to be expected with enableJK not set.

This is how I can reproduce the problem:

Starting with the domain.xml shipped with Glassfish 3.1.2 I execute the following commands:
(note: this is not the full working config but it's all that's needed to cause the error)

asadmin>

enable-secure-admin
restart-domain
create-cluster c1
create-local-instance --cluster c1 i1
create-local-instance --cluster c1 i2
start-cluster c1
create-system-properties --target i1 AJP_PORT=8010
create-system-properties --target i2 AJP_PORT=8011
start-cluster

The cluster starts ok, then:

create-jvm-options --target c1 "-Dcom.sun.enterprise.web.connector.enableJK=\${AJP_PORT}"
stop-cluster
start-cluster

asadmin> start-cluster c1
remote failure: i1: Could not start instance i1 on node localhost-domain1 (local
host).

Command failed on node localhost-domain1 (localhost): Attempting to start i1....
 Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost f
rom the GlassFish install location C:\glassfish-3.1.2:

 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
i2: Could not start instance i2 on node localhost-domain1 (localhost).

Command failed on node localhost-domain1 (localhost): Attempting to start i2....
 Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost f
rom the GlassFish install location C:\glassfish-3.1.2:

 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2

The command start-instance failed for: i1 i2
Command start-cluster failed.
asadmin>

In the server log I see the following output which is generated specifically as
a result of the failing start-cluster command:


INFO: GMS1098: GMS:Announcing GroupStartup[INITIATED] for group: c1 members: i1,i2,
INFO: GMS1062: GroupStart for group: c1 State: INITIATED Starting Members: i1,i2,
INFO: Starting cluster c1
INFO: Executing start-instance on 2 instances using a thread pool of size 2: localhost-domain1:i1 localhost-domain1:i2
INFO: start-instance i1
INFO: start-instance i2
INFO: CLI801 Instance is already synchronized
INFO: CLI801 Instance is already synchronized
INFO: Attempting to start i1.... Please look at the server log for more details.....
INFO: Attempting to start i2.... Please look at the server log for more details.....
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i2 of group: c1
INFO: GMS1024: Adding Join member: i2 group: c1 StartupState: GROUP_STARTUP
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for ADD_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i1 of group: c1
WARNING: Could not start instance i2 on node localhost-domain1 (localhost).: Command ' C:\glassfish-3.1.2\glassfish\bin\asadmin.bat --_auxinput - --interactive=false start-local-instance --node localhost-domain1 --sync normal i2' failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i2.... Please look at the server log for more details.....: To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2
SEVERE: i2: Could not start instance i2 on node localhost-domain1 (localhost).
Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i2.... Please look at the server log for more details.....
To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i2
WARNING: Could not start instance i1 on node localhost-domain1 (localhost).: Command ' C:\glassfish-3.1.2\glassfish\bin\asadmin.bat --_auxinput - --interactive=false start-local-instance --node localhost-domain1 --sync normal i1' failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i1.... Please look at the server log for more details.....: To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
SEVERE: i1: Could not start instance i1 on node localhost-domain1 (localhost).
Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized
Attempting to start i1.... Please look at the server log for more details.....
To complete this operation run the following command locally on host localhost from the GlassFish install location C:\glassfish-3.1.2:
 bin/asadmin start-local-instance --node localhost-domain1 --sync normal i1
INFO: GMS1024: Adding Join member: i1 group: c1 StartupState: GROUP_STARTUP
SEVERE: Connection refused: no further information
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: IN_DOUBT_EVENT for member: i2 of group: c1
INFO: GMS1007: Received FailureSuspectedEvent for member: i2 of group: c1
INFO: GMS1005: Sending FailureSuspectedSignals to registered Actions. member: i2 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9173:228.9.20.47:23171:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: IN_DOUBT_EVENT for member: i1 of group: c1
INFO: GMS1007: Received FailureSuspectedEvent for member: i1 of group: c1
INFO: GMS1005: Sending FailureSuspectedSignals to registered Actions. member: i1 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for FAILURE_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9124:228.9.20.47:23171:c1:i1
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: FAILURE_EVENT for member: i2 of group: c1
INFO: GMS1019: member: i2 of group: c1 has failed
INFO: GMS1003: Sending FailureNotificationSignals to registered Actions. member: i2 ...
SEVERE: Connection refused: no further information
INFO: GMS1092: GMS View Change Received for group: c1 : Members in view for FAILURE_EVENT(before change analysis) are :
1: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9198:228.9.20.47:23171:c1:server

INFO: GMS1016: Analyzing new membership snapshot received as part of event: FAILURE_EVENT for member: i1 of group: c1
INFO: GMS1019: member: i1 of group: c1 has failed
INFO: GMS1003: Sending FailureNotificationSignals to registered Actions. member: i1 ...




Component/s web_container [ 10622 ]
Amy Roh added a comment - 13/Dec/12 09:15 PM

The com.sun.enterprise.web.connector.enableJK jvm option is deprecated. You're probably referring to an old blog. The network listener's attribute jkenabled should be used for each listener instead.

You should follow the HA admin guide or http://weblogs.java.net/blog/amyroh/archive/2012/02/15/running-glassfish-312-apache-http-server.

*Create a jk-enabled network listener targeted to the cluster either using asadmin create-network-listener command or the admin console.

asadmin> create-network-listener --protocol http-listener-1 --target cluster1 --listenerport ${AJP_PORT} --jkenabled true jk-connector

*Create the jvmRoute property targeted to the cluster using the create-jvm-options command.

asadmin> create-jvm-options --target cluster1 "-DjvmRoute=\${AJP_INSTANCE_NAME}"

*Define the AJP_PORT and AJP_INSTANCE_NAME properties for each of the instances of the cluster using the create-system-properties command. The port values need to match the values specified in the workers.properties.

asadmin> create-system-properties --target instance1 AJP_PORT=8009
asadmin> create-system-properties --target instance1 AJP_INSTANCE_NAME=instance1
asadmin> create-system-properties --target instance2 AJP_PORT=8010
asadmin> create-system-properties --target instance2 \AJP_INSTANCE_NAME=instance2
asadmin> create-system-properties --target instance3 AJP_PORT=8011


Amy Roh made changes - 04/Jan/13 08:19 PM
Status Open [ 1 ] Closed [ 6 ]
Resolution Invalid [ 6 ]