[ http://issues.apache.org/jira/browse/GERONIMO-2507?page=comments#action_12446371 ] Paul McMahan commented on GERONIMO-2507: ----------------------------------------
Disabling JSP precompilation in the geronimo-console-standard module reduced startup time for my admin console in jetty from 86s to 25s. Precompiling JSPs adds 164 servlets to the web.xml for the admin console, which I suppose must be causing the kernel to process lots more gbeans when it starts the module, at least in the jetty assembly. JSP precompilation is nice to have because it makes first time access to the admin console more snappy. However, I believe the real reason JSP precompilation was introduced was to deal with the windows path length restrictions encountered in 1.1 where the long package/class names generated by the jsp compiler, combined with the path length of the console module already in the repo, exceeded what windows could handle. Precompiling the JSPs worked around this problem by putting the compiled JSP classes in a jar instead of writing them in the repo at runtime. See GERONIMO-1844. Some of the options I can think of for dealing with this are 1.) disable JSP precompilation and deal with the windows path length problem in some other way 2.) look into what causes the delay in the jetty assembly when lots of servlets are defined in an application. i.e. what changed from geronmio 1.1.1 to 1.2? 3.) reduce the number of JSPs in the console 4.) investigate some way to make the jspc maven plugin generate fewer servlet definitions > 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
