Just to clarify:
Yes, I am aware that by default the "Dynamic Reconfiguration" cluster system
property will cause instances to restart when any sort of config or app
change is made.
But that's not what I'm seeing. Basically the DAS (via the nodeagent I'm
sure) performs some sort of health checks on cluster instances.
So if it notices a cluster instance is "unhealthy" it restarts the instance.
I'm just trying to better understand HOW the DAS determines that an instance
is unhealthy and whether we can be better alerted somehow when a restart has
occurred (short of grepping log files).
Thanks,
Sean
On 5/14/10 11:01 AM, "glassfish_at_javadesktop.org" <glassfish_at_javadesktop.org>
wrote:
> Hi,
>
> I have a cluster glassfish and everytime that a redeploy (of a specific
> application) happens the node agent restarts the instance. Same message
> |INFO|sun-appserver2.1|javax.ee.enterprise.system.nodeagent|_ThreadID=20;_Thre
> adName=Thread-24;sd2jvp02_inst01;|NAGT0017:The ProcessManager is restarting
> the server named.
>
> Here I turned of the feature related by Anissa and I'm waiting a new redeploy
> to see what happens.
>
> I will keep you updated!
> [Message sent by forum member 'mathcunha']
>
> http://forums.java.net/jive/thread.jspa?messageID=469826
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
> Please consider the environment before printing this e-mail.
--
Sean Comerford, Software Engineer
ESPN.com Site Architecture Group
Office: 860.766.6454 Cell: 860.329.5842