Hi lwhite
I don't think thats the problem as the setup-cluster.xml does this for me
At the end it displays:
create.domain:
[exec] Using port 4848 for Admin.
[exec] Using port 8080 for HTTP Instance.
[exec] Using port 7676 for JMS.
[exec] Using port 3700 for IIOP.
[exec] Using port 8181 for HTTP_SSL.
[exec] Using default port 3820 for IIOP_SSL.
[exec] Using default port 3920 for IIOP_MUTUALAUTH.
[exec] Using default port 8686 for JMX_ADMIN.
[exec] Domain being created with profile:cluster, as specified by variable
AS_ADMIN_PROFILE in configuration file.
[exec] Security Store uses: JKS
[exec] Domain domain1 created.
[exec] Admin login information for host [localhost] and port [4848] is being overwritten with credentials provided. This is because the --savelogin option
was used during create-domain command.
[exec] Login information relevant to admin user name [admin] for this domain [domain1] stored at [/root/.asadminpass] successfully.
[exec] Make sure that this file remains protected. Information stored in this file will be used by asadmin commands to manage this domain.
[delete] Deleting: /opt/glassfish/glassfish/passfile
Note the line:
[exec] Domain being created with profile:cluster, as specified by variable
AS_ADMIN_PROFILE in configuration file.
But this wouldn't address the issue that SessionData is replicated when everything is done one one host. And then breaks when a add another host.
I am doing this on a Debian - EtchBox.
Are these settings still required ? (*I think they where for 8.1 Release*)
echo 536870912 > /proc/sys/kernel/shmmax
echo 536870912 > /proc/sys/kernel/shmall
[Message sent by forum member 'sean_au' (sean_au)]
http://forums.java.net/jive/thread.jspa?messageID=241103