Skip to main content

after create-jvm-options ...connector.enableJK=\${AJP_PORT}" start-cluster fails

2 replies [Last post]
oversteer
Offline
Joined: 2011-03-28
Points: 0

When I type in this command and restart the cluster, start-cluster fails with the error
messages shown below.

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

I'm running 3.1.2 (with the two patched grizzly jars) and then thought that perhaps I
needed tomcat-ajp.jar with the 2 commons jars, and tried with them but no better. Do I
still need enableJK in 3.1.2? If so what could be causing the errors? jvmRoute is
setup correctly I'm pretty sure.

The saga of getting a 2 instance single node test cluster running with an application
deployed, load balanced & failing over correctly is entering the 2nd week now and I'm
really running out of time so any help much appreciated.

asadmin> start-domain
Waiting for domain1 to start ...................................................
......................................
Successfully started the domain : domain1
domain  Location: C:\glassfish-3.1.2\glassfish\domains\domain1
Log File: C:\glassfish-3.1.2\glassfish\domains\domain1\logs\server.log
Admin Port: 4848
Command start-domain executed successfully.
asadmin> start-cluster c1
remote failure: i1: Could not start instance i1 on node localhost-domain1 (local
host).
</pre>
<pre>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.....
</pre>
<pre>To complete this operation run the following command locally on host localhost f

rom the GlassFish install location C:\glassfish-3.1.2:
</pre>
<pre> bin/asadmin  start-local-instance --node localhost-domain1 --sync normal i1

i2: Could not start instance i2 on node localhost-domain1 (localhost).
</pre>
<pre>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.....
</pre>
<pre>To complete this operation run the following command locally on host localhost f

rom the GlassFish install location C:\glassfish-3.1.2:
</pre>
<pre> bin/asadmin  start-local-instance --node localhost-domain1 --sync normal i2

</pre>
<pre>The command start-instance failed for: i1 i2

Command start-cluster failed.
asadmin>

server.log

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: Attempting to start i1.... Please look at the server log for more details.....
INFO: CLI801 Instance is already synchronized
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: i1, MemberType: CORE, Address: 192.168.1.64:9144:228.9.105.37:15681:c1:i1
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9147:228.9.105.37:15681:c1:server
</pre>
<pre>INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i1 of group: c1

INFO: GMS1024: Adding Join member: i1 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:9144:228.9.105.37:15681:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9199:228.9.105.37:15681:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9147:228.9.105.37:15681:c1:server
</pre>
<pre>INFO: GMS1016: Analyzing new membership snapshot received as part of event: ADD_EVENT for member: i2 of group: c1

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
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
SEVERE: Connection refused: no further information
INFO: GMS1024: Adding Join member: i2 group: c1 StartupState: GROUP_STARTUP
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:9144:228.9.105.37:15681:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9199:228.9.105.37:15681:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9147:228.9.105.37:15681:c1:server
</pre>
<pre>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 IN_DOUBT_EVENT(before change analysis) are :
1: MemberId: i1, MemberType: CORE, Address: 192.168.1.64:9144:228.9.105.37:15681:c1:i1
2: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9199:228.9.105.37:15681:c1:i2
3: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9147:228.9.105.37:15681:c1:server
</pre>
<pre>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 FAILURE_EVENT(before change analysis) are :
1: MemberId: i2, MemberType: CORE, Address: 192.168.1.64:9199:228.9.105.37:15681:c1:i2
2: MemberId: server, MemberType: SPECTATOR, Address: 192.168.1.64:9147:228.9.105.37:15681:c1:server
</pre>
<pre>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 ...
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:9147:228.9.105.37:15681:c1:server
</pre>
<pre>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 ...

I then stop the domain, delete the enableJK line from domain.xml & restart and everything
starts correctly (although I've got session stickiness problems so something isn't right):

asadmin> start-domain
Waiting for domain1 to start ...................................................
............................
Successfully started the domain : domain1
domain  Location: C:\glassfish-3.1.2\glassfish\domains\domain1
Log File: C:\glassfish-3.1.2\glassfish\domains\domain1\logs\server.log
Admin Port: 4848
Command start-domain executed successfully.
asadmin> start-cluster c1
Command start-cluster executed successfully.
asadmin>

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
oversteer
Offline
Joined: 2011-03-28
Points: 0

I've now spent over a week trying to get a 2 instance single node cluster fully working
but I've still got problems with j_security_check not forwarding where it should do.

I really need to know: do I need to set com.sun.enterprise.web.connector.enableJK in
3.1.2 or not? I didn't see it in the admin guide but every blog seems to include this.

If so the fact that I've not been able to set it is a strong candidate for further
investigation, and if not I can look at other things.

Do me a favour then, someone must be able to answer this.

Thanks.

Logged as: http://java.net/jira/browse/GLASSFISH-18744

andreaxi
Offline
Joined: 2012-09-11
Points: 0

Hi oversteer, did you find an answer? I've the same doubt...
Thanks,
Andrea

amyroh
Offline
Joined: 2004-05-06
Points: 0

You do not need to use the com.sun.enterprise.web.connector.enableJK jvm
option in 3.1.2. It is deprecated.

Please use --jkenabled for network-listener described in the
documentation [1]

asadmin create-network-listener --protocol http-listener-1--listenerport 8009 --jkenabled true jk-connector

[1] http://docs.oracle.com/cd/E26576_01/doc.312/e24928/webapps.htm#gfaad

On 9/11/12 5:42 AM, forums@java.net wrote:
> Hi oversteer, did you find an answer? I've the same doubt... Thanks,
> Andrea
>
> --
>
> [Message sent by forum member 'andreaxi']
>
> View Post: http://forums.java.net/node/886018
>
>