I've been seeing this problem repeatedly as well, and looking through
the list it appears that there have been a number of complaints about
synchronization during application deployment, but I haven't seen any
references to how to address these problems.
In my case today, I had my production DAS go completely unresponsive
after a deployment, with my last top of the machine revealing all
system memory and swap consumed with a load average above 30. A hard
reboot was required to fix the problem.
Has anyone found any resolution or workaround to these problems?
Kris
On Fri, Sep 26, 2008 at 5:33 AM, CS Wong <lilwong_at_gmail.com> wrote:
> Hi,
>
> I've had my Glassfish cluster running for some time in production and
> over time I've been adding more modules to it. I have this problem
> that has been steadily getting worse over time.
>
> When I run "asadmin start-cluster <cluster-name>", I can see in both
> my instance server.log the following line:
>
> [#|2008-09-26T19:00:43.680+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|IdentityManager
> Data: User:admin|#]
>
> After a long time, then only I'd see something like the following:
>
> [#|2008-09-26T19:22:31.521+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;1307.017;|SYNC010:
> Synchronization completed in 1307.017 seconds.|#]
>
> That's like 20 minutes just for the synchronization alone... and there
> doesn't seem to be any logs at all about what is being done.
>
> Eventually, the startup would still proceed, but I'm worried about
> this. Is this considered normal behavior for a clustered environment?
> Is there anything I can do to speed things up?
>
> Thanks,
> Wong
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>