[
https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540764
]
Joe Bohn commented on GERONIMO-3586:
------------------------------------
IIUC the client is actually running on a particular server and hence a
particular container. The client can only retrieve information for that
container. Therefore, it provides no value for a client to have extraneous
interfaces available to it for another container.
It is the monitoring console (also running on a particular server/container)
that is the integration point for multiple containers. However, the monitoring
console itself does not access the stats directly.
So it would seem to me that a monitoring client is by design always limited to
one container and it provides no value to have excess interfaces available for
another container. I won't press the point much further, but I still don't see
value in the client having access to interfaces that it cannot utilize. So it
makes sense to me that we consolidate the container specific classes under the
container plugin (the intent behind GERONIMO-3587).
> monitoring plugin: collecting agent should have separate jetty and tomcat
> plugins
> ---------------------------------------------------------------------------------
>
> Key: GERONIMO-3586
> URL: https://issues.apache.org/jira/browse/GERONIMO-3586
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
> Affects Versions: 2.1
> Environment: windows
> Reporter: Viet Hung Nguyen
> Assignee: Jarek Gawor
> Attachments: geronimo-3586.patch
>
>
> The collecting agent plugin needs to have separate jetty and tomcat plugins
> in order to accommodate for the differences in container specific
> dependencies on stats implementation (.e.g JettyContainerStatsImpl and
> JettyConnectorStatsImpl). When the collecting agent was an EAR, this was not
> a problem; however, as a plugin, it is more tied down to having to specify
> all dependencies in the plugin's classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
