You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ashish Jain (JIRA)" <ji...@apache.org> on 2010/01/27 07:50:35 UTC
[jira] Closed: (GERONIMO-4951) Monitoring Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Jain closed GERONIMO-4951.
---------------------------------
Resolution: Fixed
Closing as this feature is already available in g 2.1.
> Monitoring Geronimo
> -------------------
>
> Key: GERONIMO-4951
> URL: https://issues.apache.org/jira/browse/GERONIMO-4951
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
> Affects Versions: 2.0.1
> Environment: Win2003
> Reporter: Jean-Jacques Parent
> Priority: Minor
>
> We have some preformance / stability problems with our web applications. We are taking some actions but we can't really see what's happenin within Geronimo.
> Are there any kind of tools to monitor Geronimo and eventually the deployed application.
> For the moment, we are using the JMX console from the sun jdk but it gives too few informations and we can't store them.
> What could be helpful for example is to get the http request, the thread which consumes the system resources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.