One big difference between GlassFish V2 and GlassFish 3.1 clustering is that node agents are not provided and used in GlassFish 3.1. Instead ssh is utilized. Using ssh in GlassFish 3.1 is the subject of a different future blog. In this blog I'll demonstrate how to setup a distributed GlassFish 3.1 system without node-agents or new ssh features.

The Desired Environment

DAS running on improvident

One cluster

The cluster has one instance

DAS and the instance run on different machines

Notes

The names are just the names of the machines I happened to use.

This is as simple a distributed system as possible for demonstration purposes.

machine1 = samskritam

machine2 = improvident

install the same GlassFish 3.1installation files on each machine.

DAS (domain1) is used on samskritam.

The other machine never runs DAS.

improvident has this set in its environment -- This makes it easy to run asadmin commands.

AS_ADMIN_HOST=samskritam

In the Procedure section I'm using these conventions:

I put the name of the machine where the command is running at the beginning of the line - you wouldn't type that in.

On improvident:

The instance has rendezvoused with the DAS and will be using host samskritam port 4848 for future communication.servers.server.mycluster_i1.config-ref=mycluster-configservers.server.mycluster_i1.lb-weight=100servers.server.mycluster_i1.name=mycluster_i1servers.server.mycluster_i1.node=impservers.server.mycluster_i1.node-agent-ref=improvident

When I create the instance on "improvident" shows:
HTTP connection failed with code 403, message: Forbidden
If I enable-secure-admin in "samskritam" I can connect to create the instance but the DAS sees the instance as not running.
Then I try with a local instance. When I disable the secure admin it shows it as running, when I disable it shows it as not running.
I've disable-secure-admin in "samskritam" after creating the instance in "improvident", but shows it as not running.
Any ideas of what could be happening?
Thanks