dev@glassfish.java.net

Re: v3 monitoring - restart question

From: Jerome Dochez <Jerome.Dochez_at_Sun.COM>
Date: Sat, 25 Jul 2009 23:29:23 -0700

how come emitting events does not automatically force the
MonitoringBootstrap ? There seem to be a missing dependency (emitting
events -> monitoring bootstrap) ?

prashanth, Sreeni ?

jerome

On Jul 23, 2009, at 10:36 AM, Jitendra Kotamraju wrote:

> 1. WebServicesContainer registers Deployment109StatsProvider.
> 2. WebServicesDeployer emits deploy/undeploy probe events
>
> When the app server is started with no applications:
> - MonitoringBootstrap is called which sets up
> StatsProviderManagerDelegateImpl
> - when an application is deployed,
> - WebServicesContainer is called
> - WebServiceDeployer is called to load the application. During the
> load, it emits deploy probe event
>
> Now, if the appserver is stopped and restarted
> - WebServicesContainer is called
> - WebServicesDeployer is called to load the application. During the
> load, it emits deploy probe event
> - MonitoringBootstrap is called which sets up
> StatsProviderManagerDelegateImpl
>
> As you can see, that the sequence is different for restart. I think
> the probe events are lost since StatsProviderManagerDelegateImpl is
> not even set.
>
> Jitu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>