geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viet Hung Nguyen (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3586) monitoring plugin: collecting agent should have separate jetty and tomcat plugins
Date Wed, 07 Nov 2007 16:52:50 GMT


Viet Hung Nguyen commented on GERONIMO-3586:

the mrc-server needs the container specific classes in its classloader because although I
am generically using the object Stats to get all of the stats from different components, the
object that is actually there is really of type "JettyWebConnectorStatsImpl." So all *Stats*Impl*
classes have to be visible within mrc-server's domain. If not, I will get a ClassNotFoundException.

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 why
I believe we should restructure our directories, plus it's good to have consistency in our

Additionally, I think what Joe meant was that the monitoring console can reside on a different
server, and regardless of what container that server is running, it will never see anything
Jetty or Tomcat specific because that stuff is all taken care of by the mrc-server. The mrc-server
is the only piece of this puzzle that needs to look at the Tomcat and Jetty specific items.

> monitoring plugin: collecting agent should have separate jetty and tomcat plugins
> ---------------------------------------------------------------------------------
>                 Key: GERONIMO-3586
>                 URL:
>             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.

View raw message