basic question: can nodeagents and clusters be started and can they run
without DAS up and running?
my experience is that in order to start nodeagent and it's managed
clusters, DAS must be up and running (otherwise the asadmin
start-node-agent command just hangs, see below) , but if the nodeagent
and the cluster is up and running, I can stop the DAS without any problems.
am I right in this? Isn't that a bug that nodeagent and the cluster will
not start if the DAS is down?
here is part of the nodeagent log generated when the DAS is down.
(glassfish v2 b33d on windows)
[#|2007-02-27T13:22:09.062+0100|CONFIG|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|DAS
url =
service:jmx:rmi:///jndi/rmi://fabian:8686/management/rmi-jmx-connector|#]
[#|2007-02-27T13:22:09.062+0100|CONFIG|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NodeAgent
url = service:jmx:rmi_jrmp://0.0.0.0:2130|#]
[#|2007-02-27T13:22:10.187+0100|INFO|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0038:Executing
Synchronization for node-agent With DAS|#]
[#|2007-02-27T13:22:22.406+0100|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC001:
Unable to communicate with Domain Administration Server. Skipping
synchronization.|#]
[#|2007-02-27T13:22:22.406+0100|SEVERE|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;fabian;8686;rmi_jrmp;|NAGT0028:It
appears that the Domain Administration Server (DAS) with [host=fabian],
[port=8686], [protocol=rmi_jrmp] is down. It could also mean that the
network settings on DAS machine need to be modified. If you believe that
the DAS is running, this error usually comes when the correct address is
not obtained by client.|#]
--
Peter Fabian
Sun Software
AIM/skype:fabianpetergabor