In 1.1.1, the majority of the startup delay is in the console module.
Dain suggested it's because we precompile the JSPs, so each one
becomes a servlet, so each one becomes a GBean, and starting GBeans is
what's slow. I found it hard to believe they're *that* slow, but I
don't have any factual basis for disputing the claim... :) In any
case, it would be great to investigate and optimize the startup time,
or maybe introduce an option for a module that would kick it's startup
into a background task or something.
Thanks,
Aaron
On 10/19/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
On my windows box, it takes roughtly one minute
and a half. It seems that it spends at least 30
seconds stucked at 85% ...
On 10/19/06, Kevan Miller <[EMAIL PROTECTED]> wrote:
>
> On Oct 19, 2006, at 12:26 PM, Dain Sundstrom wrote:
>
> > On Oct 19, 2006, at 9:22 AM, Dain Sundstrom wrote:
> >
> > It works for me on my mac:
> >
> > $ wget http://people.apache.org/dist/geronimo/unstable/1.2-r465304/
> > geronimo-jetty-j2ee-1.2-r465304.tar.gz
> > 09:22:36 (528.97 KB/s) - `geronimo-jetty-j2ee-1.2-r465304.tar.gz'
> > saved [49455963/49455963]
> >
> > $ tar -zxf geronimo-jetty-j2ee-1.2-r465304.tar.gz
> > tar: A lone zero block at 122798
> >
> > $ java -jar geronimo-jetty-j2ee-1.2-r465304/bin/server.jar
> > [************************] 100% 42s Startup complete
>
> Ah. I was using a 1.4 JRE. I switched to 1.5 and it starts OK.
>
> Wow. Startup time is way slower than 1.1.1. Starting the webconsole
> config took over 30 seconds. Anybody know what's going on?
>
> --kevan
>
--
Cheers,
Guillaume Nodet
