Jeanfrancois,
I need to understand this more. The monitoring level for http-service
(under module-monitoring-levels) is turned off by default. So, there
shouldn't be any overhead related to monitoring on Grizzly side. Can you
please give me more details for the following statement.
/"We have observed some performance regressions recently at runtime
and one reason is the fact that the Monitoring & Management support
(implemented as GrizzlyAdapter) are *always* registered as startup. "/
thanks
Prashanth
Jeanfrancois Arcand wrote:
> Hi,
>
> we recently observed a performance regression when
> monitoring/management got enabled:
>
> * https://glassfish.dev.java.net/issues/show_bug.cgi?id=9286
>
> The problem is the GrizzlyAdapter used for implementing the features
> are registered on port 8080, 8181, etc. Should they be only registered
> on port 4848 like all the GrizzlyAdapter used by to support admin? Why
> do they need to be available on all port?
>
> Thanks
>
> -- Jeanfrancois
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>