Minimize the JBoss memory footprint when multiple wars have common components
Issue
- We are having problems with out of memory issues in our production environment. We have 9 WAR files for separate web applications, but which have significant common components. We are trying to determine the best approach to reduce the memory footprint. The average size of each war is around 40 MB, and the total is 372 MB.
- Should we pull out the common JARs, but still keep the web apps independent. Since they are separate web apps, will this help or will the overall memory footprint still remain about the same?
- Should we pull out the common JARs, but then package everything together in a single EAR but still with separate web apps? Is there a maximum size of an EAR that is deployed?
- Should we combine the web apps into a single app (WAR) and ensure there is only one copy of any JAR in the app? Our concern there is if there is a maximum size of a WAR file?
Environment
- JBoss Enterprise Application Platform (EAP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
