asadmin start-node-agent timesout after 15 mins
I am try to set up a cluster of two machines but when I try to start the node agent for the second machine (the one not running the DAS) the command hangs.
Please notice that I have the following situation:
1) Node agent on machine1 starts correctly
2) DAS on machine1 knows about node agent on machine2 (rendezvousOccurred=true). This, in my opinion, should prove that communication between boxes occurs correctly and that the node agent on machine2 was correctly created.
3) I did some packet sniffing in my network. When the node agent on machine2 tries to start up there is indeed some communication between the boxes on port 8686, but I could not read anything useful in the data of the packets.
This is an extract of the log for the node agent on machine2:
[#|2008-12-30T11:47:48.747+0900|INFO|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0038:Executing Synchronization for node-agent With DAS|#]
[#|2008-12-30T12:02:56.595+0900|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-12-30T12:02:56.599+0900|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-12-30T12:02:58.605+0900|WARNING|sun-appserver9.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0013:Stopping Node Agent...|#]
Note that there is 15 minutes difference between the first line and the others. There is clearly a timeout somewhere.
Has anybody seen this behavior before? Is there any log at the DAS side I can look at?
Thanks in advance for your kind reply,