Unloading policies for unused classes and custom modules in Jboss EAP 6
Issue
Concerns related to the use of the Heap Memory of JVM.
-
At what point classes into a custom module are loaded ?
-
Are unused classes unloaded? Which is the policy?
-
Are there any limit in the number of the resources in a custom module? When this resources are loaded ? During the start-up ? At the first invocation?
-
Are there any policy to unload unused custom modules ?
Environment
- Red Hat JBoss Enterprise Application Platform
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.