[ 
https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540811
 ] 

Anita Kulshreshtha commented on GERONIMO-3586:
----------------------------------------------

>For the instance of Tomcat, it works fine because mrc-server depends on MEJB 
>which depends on G-management, which is where the Tomcat stuff >is located. 
>However, since Jetty is still in G-jetty6 and nothing depends on it, it fails 
>to be visible by the mrc-server.
      This is a perfect example of why the Jetty*Stats and Jetty*StatsImpl 
classes should be in g-management and not in g-jetty6. Otherwise we will need 
two versions of Monitoring console (client, mrc-server,..).
     Though you could use JSR77 to get all the info you need from any 
StatsImpl, e.g. if a StatsImpl (could be a Jetty*StatsImpl)  has a statistic 
named XYX, it will have a method named getXYZ. Using this you could get all 
Statistics in the StatsImpl. 
      The mrc-server also consumes too many resources, in its current form it 
can not be loaded in the same JVM as the server to be monitored.

> 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.

Reply via email to