Hallo,
I hope someone can help me. I tried to set up a Glassfish cluster, but the cluster node was not able to communicate to the admin node.
Here is the way I tried it:
1) Hardware/Software
--------------------
Administration node: 192.168.1.42
Cluster node: 192.168.1.43
OS: both Fedora 8 X86_64 (xen, DomU)
No firewall, SELinux disabled, ping/nmap works in both directions
> java -version:
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
Glassfish: v2ur2-b04-linux
2) Installation
---------------
see
http://www.manorrock.com/documents/glassfish/cluster.html
2.1) Administration node
------------------------
# Install glassfish
> cd /opt/
> java -Xmx256M -jar glassfish-installer-v2ur2-b04-linux.jar
> cd glassfish/
> chmod -R a+x lib/ant/bin/
> lib/ant/bin/ant -f setup-cluster.xml
# Start domain
> bin/asadmin start-domain
# Create cluster
> bin/asadmin create-cluster --host 192.168.1.42 --port 4848 cluster1
2.2) Cluster node
-----------------
# Install glassfish
> cd /opt/
> java -Xmx256M -jar glassfish-installer-v2ur2-b04-linux.jar
> cd glassfish/
> chmod -R a+x lib/ant/bin/
> lib/ant/bin/ant -f setup-cluster.xml
# Create node agent
> bin/asadmin create-node-agent --host 192.168.1.42 --port 4848 cluster1-node43-agent
---
# Check node agent on admin node
> bin/asadmin list-node-agents
cluster1-node43-agent not running
Command list-node-agents executed successfully.
---
# Trying to start node
> bin/asadmin start-node-agent cluster1-node43-agent
Redirecting output to /opt/glassfish/nodeagents/cluster1-node43-agent/agent/logs/server.log
Redirecting application output to /opt/glassfish/nodeagents/cluster1-node43-agent/agent/logs/server.log
Node Agent cluster1-node43-agent failed to startup. Please check the server log for more details.
CLI137 Command start-node-agent failed.
3) Trying to find the error
---------------------------
# Check log file on cluster node
> less /opt/glassfish/nodeagents/cluster1-node43-agent/agent/logs/server.log
Jul 11, 2008 4:11:24 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher buildCommand
INFO:
/opt/jdk1.6.0_07/jre/../bin/java
-Dcom.sun.aas.instanceRoot=/opt/glassfish/nodeagents/cluster1-node43-agent/agent
-Dcom.sun.aas.configRoot=/opt/glassfish/config
-Dcom.sun.aas.defaultLogFile=/opt/glassfish/nodeagents/cluster1-node43-agent/agent/logs/server.log
-Dcom.sun.aas.instanceName=cluster1-node43-agent
-Dcom.sun.aas.isNodeAgent=true
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.appserv.admin.pluggable.features=com.sun.enterprise.ee.admin.pluggable.EEClientPluggableFeatureImpl
-Dcom.sun.appserv.nss.db=/opt/glassfish/nodeagents/cluster1-node43-agent/agent/config
-Dcom.sun.appserv.pluggable.features=com.sun.enterprise.ee.server.pluggable.EEPluggableFeatureImpl
-Djava.endorsed.dirs=/opt/glassfish/lib/endorsed
-Djava.library.path=/opt/glassfish/lib:/opt/glassfish/lib:/opt/glassfish/lib
-Djava.security.auth.login.config=/opt/glassfish/nodeagents/cluster1-node43-agent/agent/config/login.conf
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Djmx.invoke.getters=true
-XX:+UnlockDiagnosticVMOptions
-XX:LogFile=/opt/glassfish/nodeagents/cluster1-node43-agent/agent/logs/jvm.log
-XX:+LogVMOutput
-cp
/opt/glassfish/lib/appserv-launch.jar:/opt/glassfish/lib/appserv-admin.jar:/opt/glassfish/lib/appserv-ee.jar:/opt/glassfish/lib/javaee.jar:/opt/glassfish/lib/appserv-se.jar:/opt/glassfish/lib/appserv-ext.jar:/opt/glassfish/lib/appserv-rt.jar
com.sun.enterprise.ee.nodeagent.NodeAgentMain
start
startInstancesOverride=NOTSET
syncInstances=false
[#|2008-07-11T16:11:24.297+0200|INFO|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|IdentityManager Data: User:admin|#]
[#|2008-07-11T16:11:24.368+0200|INFO|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0004:Starting Node Agent...|#]
[#|2008-07-11T16:11:24.378+0200|CONFIG|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|DAS url = service:jmx:rmi:///jndi/rmi://192.168.1.42:8686/management/rmi-jmx-connector|#]
[#|2008-07-11T16:11:24.432+0200|INFO|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0025:The node agent could not configure logging levels. Default logging level will be used.|#]
[#|2008-07-11T16:11:24.432+0200|INFO|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0038:Executing Synchronization for node-agent With DAS|#]
[#|2008-07-11T16:11:33.517+0200|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC001: Unable to communicate with Domain Administration Server. Skipping synchronization.|#]
[#|2008-07-11T16:11:33.518+0200|SEVERE|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0035:The NodeAgent failed to complete the intial synchronization with the DAS. Please make sure the DAS is running and is accessible from the NodeAgents server|#]
[#|2008-07-11T16:11:35.522+0200|WARNING|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0013:Stopping Node Agent...|#]
# Check log file on admin node
> tail /opt/glassfish/domains/domain1/logs/server.log
[#|2008-07-11T16:03:51.350+0200|INFO|sun-appserver9.1|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=16;_ThreadName=httpWorkerThread-4848-1;;|Initializing Sun's JavaServer Faces implementation (1.2_04-b20-p03) for context ''|#]
[#|2008-07-11T16:04:00.458+0200|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-0;|ClustersConfigMBean.createCluster called with: [clusterName=cluster1][configName=null][props=null][hosts=null][haagentport=null][haadminpassword=null][haadminpasswordfile=null][devicesize=512][haprops=null][autohadb=false][portbase=null]|#]
[#|2008-07-11T16:04:01.515+0200|INFO|sun-appserver9.1|com.sun.jbi.management.DeploymentService|_ThreadID=17;_ThreadName=httpWorkerThread-4848-0;|JBIMA0452: Successfully processed 0 Service Assemblies during startup.|#]
[#|2008-07-11T16:04:01.515+0200|INFO|sun-appserver9.1|com.sun.jbi.framework|_ThreadID=17;_ThreadName=httpWorkerThread-4848-0;|JBIFW0012: JBI framework startup complete.|#]
[#|2008-07-11T16:04:01.515+0200|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-0;|amx:j2eeType=X-J2EECluster,name=cluster1 is registered.|#]
# Check network connection on cluster node
nmap 192.168.1.42 -p 1-65535
Starting Nmap 4.52 ( http://insecure.org ) at 2008-07-11 16:18 CEST
Interesting ports on mas2036.adm-group.com (192.168.1.42):
Not shown: 65520 closed ports
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
3700/tcp open unknown
3820/tcp open unknown
3920/tcp open unknown
4848/tcp open unknown
7676/tcp open unknown
8080/tcp open http-proxy
8181/tcp open unknown
8686/tcp open unknown
34176/tcp open unknown
39350/tcp open unknown
53075/tcp open unknown
56646/tcp open unknown
59507/tcp open unknown
MAC Address: 00:16:3E:29:C2:0C (Xensource)
Nmap done: 1 IP address (1 host up) scanned in 1.414 seconds
Does anyone have an idea what went wrong?
Thanx in advance,
Holger
[Message sent by forum member 'skydiver2311' (skydiver2311)]
http://forums.java.net/jive/thread.jspa?messageID=286021