[ http://issues.apache.org/jira/browse/GERONIMO-2507?page=comments#action_12446379 ] Jeff Genender commented on GERONIMO-2507: -----------------------------------------
The fact that this is hitting Jetty very likely due to the fact that each servlet is a GBean. Removing jsp precompilation is a treatment to a problem and not the panacea. Notice this is not an issue with Tomcat with the difference being it does not create a separate GBean for each servlet. Ths jsp-maven-plugin simply creates a servlet for each JSP which is the standard for precompiling JSPs (see the jasper/jspc doc on the Tomcat website http://tomcat.apache.org/tomcat-5.5-doc/jasper-howto.html)...I cannot see this playing a significant component in this. This becomes an issue for folks that have fairly large JSP applications. I would not recommend removing JSP precompilation nor reduce JSPs and deal with the problem head on. I think #2 in the listed options by Paul is the appropriate action to take. I think #1, #3, and #4 are red herrings. > Starting the webconsole config is taking *way* too much time > ------------------------------------------------------------ > > Key: GERONIMO-2507 > URL: http://issues.apache.org/jira/browse/GERONIMO-2507 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Affects Versions: 1.2 > Reporter: Kevan Miller > Priority: Critical > Fix For: 1.2 > > > Server startup time of 1.2 has more than doubled. The vast majority of time > is being spent starting the webconsole config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
