You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rakesh Midha (JIRA)" <ji...@apache.org> on 2007/01/05 08:19:27 UTC
[jira] Updated: (GERONIMO-2690) New view for all the classloaders
and classes loaded in it
[ https://issues.apache.org/jira/browse/GERONIMO-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rakesh Midha updated GERONIMO-2690:
-----------------------------------
Attachment: classloader.gif
classloaderView2690.patch
common.patch
> New view for all the classloaders and classes loaded in it
> ----------------------------------------------------------
>
> Key: GERONIMO-2690
> URL: https://issues.apache.org/jira/browse/GERONIMO-2690
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.0
> Environment: Any
> Reporter: Rakesh Midha
> Assigned To: Rakesh Midha
> Fix For: 2.0
>
> Attachments: classloader.gif, classloaderView2690.patch, common.patch
>
>
> Looking into the classloader problems and knowing which classsloader loaded which class has always been a big problem in app servers.
> So many times we hit ClassNotFoundException and wonder why is it happening when the classes are available in my module. It may be because those classes are loaded by some other classloader.
> I think it would be nice if we can add a view in console which shows are the classloaders and the classes they loaded.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira