users@glassfish.java.net

Re: Maximum Deployment Size? was (RE: Cluster SynchronizationException)

From: <glassfish_at_javadesktop.org>
Date: Mon, 21 Jul 2008 22:10:04 PDT

Daniel & Manfred,

Thanks for your continued help and for the recent suggestion.

First the good news:

With a completely clean installation of the DAS and node agent (each on separate
servers – same subnet) and with the INSTANCE-SYNC-JVM-OPTIONS property set
to -Xmx256m we no longer see the OutOfMemoryException.

The bad news is that the node agent failed to start, timing out after approximately 20 minutes.
The application directory for the instance contains 2 out of the 9 war files and the
SynchronizationMain process is still running. There are no exceptions in the log files
on the instance side.

The logs on the DAS side contain entries of the form:

[#|2008-07-22T12:48:45.289+1000|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=15;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-670762051/webapp-a.war;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-670762051/webapp-a.war]|#]

[#|2008-07-22T12:48:53.079+1000|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=15;_ThreadName=httpWorkerThread-4848-1;No route to host;_RequestID=d0789af5-f3b7-42b5-8acb-c370347ff6b7;|EEADM0221: Auto Apply changes could not be done [No route to host]|#]

[#|2008-07-22T12:48:56.113+1000|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=42;_ThreadName=event-handler-0;
web-01;_RequestID=cee91dde-4a7c-4a7d-900c-75e9e8c69228;|EEADM0068: Instance web-01 is not reachable.|#]

[#|2008-07-22T12:50:54.673+1000|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=44;_ThreadName=RMI TCP Connection(11)-192.168.100.31;Tue Jul 22 12:50:54 EST 2008;na-vm1;|SYNC005: Received synchronization request at time [Tue Jul 22 12:50:54 EST 2008] from [na-vm1].|#]

I suspect that we are now hitting some other configuration issue that will require further
troubleshooting - it may be a symptom of the numerous configuration changes that we
have made along the way in order to track down the original issue.

I will try once more with clean VMs tomorrow.

Thanks.
G.
[Message sent by forum member 'gussie' (gussie)]

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