[
https://issues.apache.org/jira/browse/GERONIMO-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466599
]
Kevan Miller commented on GERONIMO-2690:
----------------------------------------
This problem was noted in the discussion regarding this patch.
Rakesh has posted a patch which reduces the amount of memory required by this
viewer. I'll look at applying the patch prior to the m2 branch. In the
meantime, you can bump your servers heap, if you want to work-around...
> 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: Kevan Miller
> Fix For: 2.0
>
> Attachments: classloader.gif, classloaderView2690.patch,
> classloaderViewLinks.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.
-
You can reply to this email to add a comment to the issue online.
