users@glassfish.java.net

Unexpected Node Agent exception

From: <glassfish_at_javadesktop.org>
Date: Tue, 04 Nov 2008 01:37:54 PST

Hi

i had created a glassfish cluster composed by 2 machines and one load balancer.
On first machine i have a DAS, a domain and first node agent.
On second machine i have the second node agent.
On first machine installation and cluster run ok.
The problem is when i try to use the second node agent.

When i try to start it for the first time i have the seguet result:
Redirecting output to /work/glassfish/nodeagents/mms-main-agent03/agent/logs/server.log
Nov 3, 2008 6:16:30 PM com.sun.enterprise.ee.nodeagent.NodeAgentMain startup
INFO: IdentityManager Data: User:admin
Redirecting application output to /work/glassfish/nodeagents/mms-main-agent03/agent/logs/server.log
Nov 3, 2008 6:16:32 PM com.sun.enterprise.ee.nodeagent.NodeAgentMain startup
INFO: NAGT0004:Starting Node Agent...
Nov 3, 2008 6:16:32 PM com.sun.enterprise.ee.nodeagent.NodeAgent configureLogger
INFO: NAGT0025:The node agent could not configure logging levels. Default logging level will be used.
Nov 3, 2008 6:16:32 PM com.sun.enterprise.ee.nodeagent.NodeAgent synchronizeWithDASInternal
INFO: NAGT0038:Executing Synchronization for node-agent With DAS
Nov 3, 2008 6:16:32 PM com.sun.enterprise.ee.nodeagent.NodeAgentMain main
SEVERE: NAGT0014:Unexpected Node Agent exception.
Throwable occurred: java.lang.ExceptionInInitializerError
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
        at com.sun.enterprise.ee.synchronization.JmxSynchronizationDriver.getPingCommand(JmxSynchronizationDriver.java:70)
        at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:167)
        at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:129)
        at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:617)
        at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:574)
        at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.run(BaseNodeAgent.java:140)
        at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:194)
        at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:265)
Caused by: java.lang.NullPointerException
        at java.util.Hashtable.get(Unknown Source)
        at com.sun.enterprise.util.i18n.StringManagerBase.getStringManager(StringManagerBase.java:133)
        at com.sun.enterprise.ee.synchronization.PingCommand.<clinit>(PingCommand.java:63)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
        ... 8 more
Node Agent mms-main-agent03 failed to startup. Please check the server log for more details.
CLI137 Command start-node-agent failed.




an on second tentative i have:

Redirecting output to /work/glassfish/nodeagents/mms-main-agent03/agent/logs/server.log
Nov 4, 2008 9:38:22 AM com.sun.enterprise.ee.nodeagent.NodeAgentMain startup
INFO: IdentityManager Data: User:admin
Redirecting application output to /work/glassfish/nodeagents/mms-main-agent03/agent/logs/server.log
Nov 4, 2008 9:38:24 AM com.sun.enterprise.ee.nodeagent.NodeAgentMain startup
INFO: NAGT0004:Starting Node Agent...
Nov 4, 2008 9:38:24 AM com.sun.enterprise.ee.nodeagent.NodeAgent configureLogger
INFO: NAGT0025:The node agent could not configure logging levels. Default logging level will be used.
Nov 4, 2008 9:38:24 AM com.sun.enterprise.ee.nodeagent.NodeAgent synchronizeWithDASInternal
INFO: NAGT0038:Executing Synchronization for node-agent With DAS
Nov 4, 2008 9:38:24 AM com.sun.enterprise.ee.nodeagent.NodeAgentMain main
SEVERE: NAGT0014:Unexpected Node Agent exception.
Throwable occurred: java.lang.ExceptionInInitializerError
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
        at com.sun.enterprise.ee.synchronization.JmxSynchronizationDriver.getPingCommand(JmxSynchronizationDriver.java:70)
        at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:167)
        at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:129)
        at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:617)
        at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:574)
        at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.run(BaseNodeAgent.java:140)
        at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:194)
        at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:265)
Caused by: java.lang.NullPointerException
        at java.util.Hashtable.get(Unknown Source)
        at com.sun.enterprise.util.i18n.StringManagerBase.getStringManager(StringManagerBase.java:133)
        at com.sun.enterprise.ee.synchronization.PingCommand.<clinit>(PingCommand.java:63)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
        ... 8 more
Timeout waiting for Node Agent mms-main-agent03 to go to starting state.
CLI137 Command start-node-agent failed.


As u can see i have a timeout.



If i log in on first machine console and i control under cluster section i can see al 2 the nodes registered in the cluster ... but the second don't run really.


Any suggests?!


IMPORTANT: the second machine is a G4 mac machine based.
[Message sent by forum member 'obylan' (obylan)]

http://forums.java.net/jive/thread.jspa?messageID=314720