[
https://jira.jboss.org/browse/JBAS-8394?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert updated JBAS-8394:
-------------------------------
Summary: Slow startup for large numbers of JSF applications (was: Slow startup
for lots of JSF applications)
Description:
It looks like the JSF Deployer can cause slow startup if many different JSF applications
are deployed. In my testing, it adds about 3 seconds for each JSF deployment. My tests
are not conclusive, but I'm guessing that since JSF is now loaded by the WAR's
classloader instead of Tomcat's classloader then the JSF classes have to be reloaded
for each JSF app. I suspect that this causes extra memory usage as well over the old way
of doing it.
The solution is to allow all WARs that use the same JSF configuration to share the same
classloader for those classes.
I suspect that other deployers such as the Weld deployer and Seam deployer have the same
issue. This would be a problem for any deployer that adds jars to the deloyment classpath
on the fly.
was:
It looks like the JSF Deployer can cause slow startup if lots of different JSF
applications are deployed. In my testing, it adds about 3 seconds for each JSF
deployment. My tests are not conclusive, but I'm guessing that since JSF is now
loaded by the WAR's classloader instead of Tomcat's classloader then the JSF
classes have to be reloaded for each JSF app. I suspect that this causes extra memory
usage as well over the old way of doing it.
The solution is to allow all WARs that use the same JSF configuration to share the same
classloader for those classes.
I suspect that other deployers such as the Weld deployer and Seam deployer have the same
issue. This would be a problem for any deployer that adds jars to the deloyment classpath
on the fly.
Slow startup for large numbers of JSF applications
--------------------------------------------------
Key: JBAS-8394
URL:
https://jira.jboss.org/browse/JBAS-8394
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JSF
Affects Versions: 6.0.0.M4
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 6.0.0.Final
It looks like the JSF Deployer can cause slow startup if many different JSF applications
are deployed. In my testing, it adds about 3 seconds for each JSF deployment. My tests
are not conclusive, but I'm guessing that since JSF is now loaded by the WAR's
classloader instead of Tomcat's classloader then the JSF classes have to be reloaded
for each JSF app. I suspect that this causes extra memory usage as well over the old way
of doing it.
The solution is to allow all WARs that use the same JSF configuration to share the same
classloader for those classes.
I suspect that other deployers such as the Weld deployer and Seam deployer have the same
issue. This would be a problem for any deployer that adds jars to the deloyment classpath
on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira