You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Dain Sundstrom <da...@apache.org> on 2006/10/18 23:19:37 UTC
Weekly: Geronimo 1.2-r465304
Geronimo 1.2-r465304 - Oct 18, 2006
http://people.apache.org/dist/geronimo/unstable/1.2-r465304/
geronimo-1.2-r465304-src.tar.gz
geronimo-1.2-r465304-src.zip
geronimo-framework-1.2-r465304.tar.gz
geronimo-framework-1.2-r465304.zip
geronimo-jetty-j2ee-1.2-r465304.tar.gz
geronimo-jetty-j2ee-1.2-r465304.zip
geronimo-jetty-minimal-1.2-r465304.tar.gz
geronimo-jetty-minimal-1.2-r465304.zip
geronimo-tomcat-j2ee-1.2-r465304.tar.gz
geronimo-tomcat-j2ee-1.2-r465304.zip
geronimo-tomcat-minimal-1.2-r465304.tar.gz
geronimo-tomcat-minimal-1.2-r465304.zip
Changelog:
http://people.apache.org/dist/geronimo/unstable/1.2-r465304/CHANGELOG.txt
NOTE: This build is not an official release, nor tested, and should be
considered unstable.
Re: Weekly: Geronimo 1.2-r465304
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 10/19/06, David Jencks <da...@yahoo.com> wrote:
> On Oct 19, 2006, at 1:31 PM, Aaron Mulder wrote:
> > Looking at the 1.2 results: webconsole-jetty in 27s and
> > webconsole-tomcat in < 5s.... That suggests GBeans aren't the whole
> > problem...
>
> Actually that suggests gbeans are the problem since jetty has gbeans
> for each servlet, servlet filter, etc etc, whereas tomcat doesn't,
> just one that basically holds the web.xml.
Aha! I had forgotten that.
Thanks,
Aaron
Re: Weekly: Geronimo 1.2-r465304
Posted by David Jencks <da...@yahoo.com>.
On Oct 19, 2006, at 1:31 PM, Aaron Mulder wrote:
> Looking at the 1.2 results: webconsole-jetty in 27s and
> webconsole-tomcat in < 5s.... That suggests GBeans aren't the whole
> problem...
Actually that suggests gbeans are the problem since jetty has gbeans
for each servlet, servlet filter, etc etc, whereas tomcat doesn't,
just one that basically holds the web.xml.
thanks
david jencks
>
> Thanks,
> Aaron
>
> On 10/19/06, Dain Sundstrom <da...@iq80.com> wrote:
>> On Oct 19, 2006, at 12:26 PM, Kevan Miller wrote:
>>
>> >
>> > On Oct 19, 2006, at 2:27 PM, Aaron Mulder wrote:
>> >
>> >> 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.
>> >
>> > Agreed that some optimization would be nice. However, this isn't
>> > really a case of "optimization", I think. Something has changed
>> > quite drastically between 1.1.1 and 1.2-SNAPSHOT. We've more than
>> > doubled our startup time...
>>
>> My guess is we have doubled the number of jsp pages and thus the
>> number of GBeans.
>>
>> -dain
>>
>> Here are the numbers from 1.2 jetty:
>>
>> Module 1/22 org.apache.geronimo.configs/rmi-naming/1.2-r465304/
>> car started in .274s
>> Module 2/22 org.apache.geronimo.configs/j2ee-server/1.2-r465304/
>> car started in .143s
>> Module 3/22 org.apache.geronimo.configs/transaction/1.2-r465304/
>> car started in .243s
>> Module 4/22 org.apache.geronimo.configs/j2ee-security/1.2-r465304/
>> car started in .333s
>> Module 5/22 org.apache.geronimo.configs/axis/1.2-r465304/
>> car started in .044s
>> Module 6/22 org.apache.geronimo.configs/openejb/1.2-r465304/
>> car started in 1.785s
>> Module 7/22 org.apache.geronimo.configs/system-database/1.2-r465304/
>> car started in .000s
>> Module 9/22 org.apache.geronimo.configs/activemq/1.2-r465304/
>> car started in .239s
>> Module 10/22 org.apache.geronimo.configs/jetty/1.2-r465304/
>> car started in .533s
>> Module 11/22 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2-
>> r465304/car started in .183s
>> Module 12/22 org.apache.geronimo.configs/j2ee-deployer/1.2-r465304/
>> car started in .203s
>> Module 13/22 org.apache.geronimo.configs/connector-deployer/1.2-
>> r465304/car started in .128s
>> Module 14/22 org.apache.geronimo.configs/openejb-deployer/1.2-
>> r465304/
>> car started in .302s
>> Module 15/22 org.apache.geronimo.configs/client-deployer/1.2-r465304/
>> car started in .067s
>> Module 16/22 org.apache.geronimo.configs/axis-deployer/1.2-r465304/
>> car started in .585s
>> Module 17/22 org.apache.geronimo.configs/sharedlib/1.2-r465304/
>> car started in .007s
>> Module 18/22 org.apache.geronimo.configs/jetty-deployer/1.2-r465304/
>> car started in .259s
>> Module 19/22 org.apache.geronimo.configs/welcome-jetty/1.2-r465304/
>> car started in .452s
>> Module 20/22 org.apache.geronimo.configs/webconsole-jetty/1.2-
>> r465304/
>> car started in 27.210s
>> Module 21/22 org.apache.geronimo.configs/remote-deploy-jetty/1.2-
>> r465304/car started in .190s
>> Module 22/22 org.apache.geronimo.configs/hot-deployer/1.2-r465304/
>> car started in .278s
>>
>> And from 1.1 jetty;
>>
>> Booting Geronimo Kernel (in Java 1.4.2_09)...
>> Module 1/20 geronimo/rmi-naming/1.1.1/car started
>> in .
>> 206s
>> Module 2/20 geronimo/j2ee-server/1.1.1/car started
>> in .
>> 350s
>> Module 3/20 geronimo/j2ee-security/1.1.1/car started
>> in .
>> 339s
>> Module 4/20 geronimo/axis/1.1.1/car started
>> in .
>> 049s
>> Module 5/20 geronimo/openejb/1.1.1/car started
>> in .
>> 232s
>> Module 6/20 geronimo/system-database/1.1.1/car started in
>> 1.521s
>> Module 7/20 geronimo/activemq-broker/1.1.1/car started
>> in .
>> 810s
>> Module 8/20 geronimo/activemq/1.1.1/car started
>> in .
>> 218s
>> Module 9/20 geronimo/jetty/1.1.1/car started
>> in .
>> 445s
>> Module 10/20 geronimo/geronimo-gbean-deployer/1.1.1/car started
>> in .
>> 180s
>> Module 11/20 geronimo/j2ee-deployer/1.1.1/car started
>> in .
>> 163s
>> Module 12/20 geronimo/openejb-deployer/1.1.1/car started
>> in .
>> 187s
>> Module 13/20 geronimo/client-deployer/1.1.1/car started
>> in .
>> 036s
>> Module 14/20 geronimo/axis-deployer/1.1.1/car started
>> in .
>> 050s
>> Module 15/20 geronimo/sharedlib/1.1.1/car started
>> in .
>> 005s
>> Module 16/20 geronimo/jetty-deployer/1.1.1/car started
>> in .
>> 181s
>> Module 17/20 geronimo/welcome-jetty/1.1.1/car started
>> in .
>> 441s
>> Module 18/20 geronimo/webconsole-jetty/1.1.1/car started in
>> 7.797s
>> Module 19/20 geronimo/remote-deploy-jetty/1.1.1/car started
>> in .
>> 165s
>> Module 20/20 geronimo/hot-deployer/1.1.1/car started
>> in .
>> 220s
>>
>> And tomcat 1.2
>>
>> Module 1/22 org.apache.geronimo.configs/rmi-naming/1.2-r465304/
>> car started in .282s
>> Module 2/22 org.apache.geronimo.configs/j2ee-server/1.2-r465304/
>> car started in .142s
>> Module 3/22 org.apache.geronimo.configs/transaction/1.2-r465304/
>> car started in .212s
>> Module 4/22 org.apache.geronimo.configs/j2ee-security/1.2-r465304/
>> car started in .325s
>> Module 5/22 org.apache.geronimo.configs/axis/1.2-r465304/
>> car started in .044s
>> Module 6/22 org.apache.geronimo.configs/openejb/1.2-r465304/
>> car started in 2.236s
>> Module 7/22 org.apache.geronimo.configs/system-database/1.2-r465304/
>> car started in .000s
>> Module 8/22 org.apache.geronimo.configs/activemq-broker/1.2-r465304/
>> car started in 1.155s
>> Module 9/22 org.apache.geronimo.configs/activemq/1.2-r465304/
>> car started in .239s
>> Module 10/22 org.apache.geronimo.configs/tomcat/1.2-r465304/
>> car started in 1.588s
>> Module 11/22 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2-
>> r465304/car started in .292s
>> Module 12/22 org.apache.geronimo.configs/j2ee-deployer/1.2-r465304/
>> car started in .206s
>> Module 13/22 org.apache.geronimo.configs/connector-deployer/1.2-
>> r465304/car started in .131s
>> Module 14/22 org.apache.geronimo.configs/openejb-deployer/1.2-
>> r465304/
>> car started in .306s
>> Module 15/22 org.apache.geronimo.configs/client-deployer/1.2-r465304/
>> car started in .066s
>> Module 16/22 org.apache.geronimo.configs/axis-deployer/1.2-r465304/
>> car started in .492s
>> Module 17/22 org.apache.geronimo.configs/sharedlib/1.2-r465304/
>> car started in .007s
>> Module 18/22 org.apache.geronimo.configs/tomcat-deployer/1.2-r465304/
>> car started in .087s
>> Module 19/22 org.apache.geronimo.configs/welcome-tomcat/1.2-r465304/
>> car started in .204s
>> Module 20/22 org.apache.geronimo.configs/webconsole-tomcat/1.2-
>> r465304/car started in 4.658s
>> Module 21/22 org.apache.geronimo.configs/remote-deploy-tomcat/1.2-
>> r465304/car started in .373s
>> Module 22/22 org.apache.geronimo.configs/hot-deployer/1.2-r465304/
>> car started in .260s
>>
Re: Weekly: Geronimo 1.2-r465304
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Looking at the 1.2 results: webconsole-jetty in 27s and
webconsole-tomcat in < 5s.... That suggests GBeans aren't the whole
problem...
Thanks,
Aaron
On 10/19/06, Dain Sundstrom <da...@iq80.com> wrote:
> On Oct 19, 2006, at 12:26 PM, Kevan Miller wrote:
>
> >
> > On Oct 19, 2006, at 2:27 PM, Aaron Mulder wrote:
> >
> >> 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.
> >
> > Agreed that some optimization would be nice. However, this isn't
> > really a case of "optimization", I think. Something has changed
> > quite drastically between 1.1.1 and 1.2-SNAPSHOT. We've more than
> > doubled our startup time...
>
> My guess is we have doubled the number of jsp pages and thus the
> number of GBeans.
>
> -dain
>
> Here are the numbers from 1.2 jetty:
>
> Module 1/22 org.apache.geronimo.configs/rmi-naming/1.2-r465304/
> car started in .274s
> Module 2/22 org.apache.geronimo.configs/j2ee-server/1.2-r465304/
> car started in .143s
> Module 3/22 org.apache.geronimo.configs/transaction/1.2-r465304/
> car started in .243s
> Module 4/22 org.apache.geronimo.configs/j2ee-security/1.2-r465304/
> car started in .333s
> Module 5/22 org.apache.geronimo.configs/axis/1.2-r465304/
> car started in .044s
> Module 6/22 org.apache.geronimo.configs/openejb/1.2-r465304/
> car started in 1.785s
> Module 7/22 org.apache.geronimo.configs/system-database/1.2-r465304/
> car started in .000s
> Module 9/22 org.apache.geronimo.configs/activemq/1.2-r465304/
> car started in .239s
> Module 10/22 org.apache.geronimo.configs/jetty/1.2-r465304/
> car started in .533s
> Module 11/22 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2-
> r465304/car started in .183s
> Module 12/22 org.apache.geronimo.configs/j2ee-deployer/1.2-r465304/
> car started in .203s
> Module 13/22 org.apache.geronimo.configs/connector-deployer/1.2-
> r465304/car started in .128s
> Module 14/22 org.apache.geronimo.configs/openejb-deployer/1.2-r465304/
> car started in .302s
> Module 15/22 org.apache.geronimo.configs/client-deployer/1.2-r465304/
> car started in .067s
> Module 16/22 org.apache.geronimo.configs/axis-deployer/1.2-r465304/
> car started in .585s
> Module 17/22 org.apache.geronimo.configs/sharedlib/1.2-r465304/
> car started in .007s
> Module 18/22 org.apache.geronimo.configs/jetty-deployer/1.2-r465304/
> car started in .259s
> Module 19/22 org.apache.geronimo.configs/welcome-jetty/1.2-r465304/
> car started in .452s
> Module 20/22 org.apache.geronimo.configs/webconsole-jetty/1.2-r465304/
> car started in 27.210s
> Module 21/22 org.apache.geronimo.configs/remote-deploy-jetty/1.2-
> r465304/car started in .190s
> Module 22/22 org.apache.geronimo.configs/hot-deployer/1.2-r465304/
> car started in .278s
>
> And from 1.1 jetty;
>
> Booting Geronimo Kernel (in Java 1.4.2_09)...
> Module 1/20 geronimo/rmi-naming/1.1.1/car started in .
> 206s
> Module 2/20 geronimo/j2ee-server/1.1.1/car started in .
> 350s
> Module 3/20 geronimo/j2ee-security/1.1.1/car started in .
> 339s
> Module 4/20 geronimo/axis/1.1.1/car started in .
> 049s
> Module 5/20 geronimo/openejb/1.1.1/car started in .
> 232s
> Module 6/20 geronimo/system-database/1.1.1/car started in
> 1.521s
> Module 7/20 geronimo/activemq-broker/1.1.1/car started in .
> 810s
> Module 8/20 geronimo/activemq/1.1.1/car started in .
> 218s
> Module 9/20 geronimo/jetty/1.1.1/car started in .
> 445s
> Module 10/20 geronimo/geronimo-gbean-deployer/1.1.1/car started in .
> 180s
> Module 11/20 geronimo/j2ee-deployer/1.1.1/car started in .
> 163s
> Module 12/20 geronimo/openejb-deployer/1.1.1/car started in .
> 187s
> Module 13/20 geronimo/client-deployer/1.1.1/car started in .
> 036s
> Module 14/20 geronimo/axis-deployer/1.1.1/car started in .
> 050s
> Module 15/20 geronimo/sharedlib/1.1.1/car started in .
> 005s
> Module 16/20 geronimo/jetty-deployer/1.1.1/car started in .
> 181s
> Module 17/20 geronimo/welcome-jetty/1.1.1/car started in .
> 441s
> Module 18/20 geronimo/webconsole-jetty/1.1.1/car started in
> 7.797s
> Module 19/20 geronimo/remote-deploy-jetty/1.1.1/car started in .
> 165s
> Module 20/20 geronimo/hot-deployer/1.1.1/car started in .
> 220s
>
> And tomcat 1.2
>
> Module 1/22 org.apache.geronimo.configs/rmi-naming/1.2-r465304/
> car started in .282s
> Module 2/22 org.apache.geronimo.configs/j2ee-server/1.2-r465304/
> car started in .142s
> Module 3/22 org.apache.geronimo.configs/transaction/1.2-r465304/
> car started in .212s
> Module 4/22 org.apache.geronimo.configs/j2ee-security/1.2-r465304/
> car started in .325s
> Module 5/22 org.apache.geronimo.configs/axis/1.2-r465304/
> car started in .044s
> Module 6/22 org.apache.geronimo.configs/openejb/1.2-r465304/
> car started in 2.236s
> Module 7/22 org.apache.geronimo.configs/system-database/1.2-r465304/
> car started in .000s
> Module 8/22 org.apache.geronimo.configs/activemq-broker/1.2-r465304/
> car started in 1.155s
> Module 9/22 org.apache.geronimo.configs/activemq/1.2-r465304/
> car started in .239s
> Module 10/22 org.apache.geronimo.configs/tomcat/1.2-r465304/
> car started in 1.588s
> Module 11/22 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2-
> r465304/car started in .292s
> Module 12/22 org.apache.geronimo.configs/j2ee-deployer/1.2-r465304/
> car started in .206s
> Module 13/22 org.apache.geronimo.configs/connector-deployer/1.2-
> r465304/car started in .131s
> Module 14/22 org.apache.geronimo.configs/openejb-deployer/1.2-r465304/
> car started in .306s
> Module 15/22 org.apache.geronimo.configs/client-deployer/1.2-r465304/
> car started in .066s
> Module 16/22 org.apache.geronimo.configs/axis-deployer/1.2-r465304/
> car started in .492s
> Module 17/22 org.apache.geronimo.configs/sharedlib/1.2-r465304/
> car started in .007s
> Module 18/22 org.apache.geronimo.configs/tomcat-deployer/1.2-r465304/
> car started in .087s
> Module 19/22 org.apache.geronimo.configs/welcome-tomcat/1.2-r465304/
> car started in .204s
> Module 20/22 org.apache.geronimo.configs/webconsole-tomcat/1.2-
> r465304/car started in 4.658s
> Module 21/22 org.apache.geronimo.configs/remote-deploy-tomcat/1.2-
> r465304/car started in .373s
> Module 22/22 org.apache.geronimo.configs/hot-deployer/1.2-r465304/
> car started in .260s
>
Re: Weekly: Geronimo 1.2-r465304
Posted by Dain Sundstrom <da...@iq80.com>.
On Oct 19, 2006, at 12:26 PM, Kevan Miller wrote:
>
> On Oct 19, 2006, at 2:27 PM, Aaron Mulder wrote:
>
>> 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.
>
> Agreed that some optimization would be nice. However, this isn't
> really a case of "optimization", I think. Something has changed
> quite drastically between 1.1.1 and 1.2-SNAPSHOT. We've more than
> doubled our startup time...
My guess is we have doubled the number of jsp pages and thus the
number of GBeans.
-dain
Here are the numbers from 1.2 jetty:
Module 1/22 org.apache.geronimo.configs/rmi-naming/1.2-r465304/
car started in .274s
Module 2/22 org.apache.geronimo.configs/j2ee-server/1.2-r465304/
car started in .143s
Module 3/22 org.apache.geronimo.configs/transaction/1.2-r465304/
car started in .243s
Module 4/22 org.apache.geronimo.configs/j2ee-security/1.2-r465304/
car started in .333s
Module 5/22 org.apache.geronimo.configs/axis/1.2-r465304/
car started in .044s
Module 6/22 org.apache.geronimo.configs/openejb/1.2-r465304/
car started in 1.785s
Module 7/22 org.apache.geronimo.configs/system-database/1.2-r465304/
car started in .000s
Module 9/22 org.apache.geronimo.configs/activemq/1.2-r465304/
car started in .239s
Module 10/22 org.apache.geronimo.configs/jetty/1.2-r465304/
car started in .533s
Module 11/22 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2-
r465304/car started in .183s
Module 12/22 org.apache.geronimo.configs/j2ee-deployer/1.2-r465304/
car started in .203s
Module 13/22 org.apache.geronimo.configs/connector-deployer/1.2-
r465304/car started in .128s
Module 14/22 org.apache.geronimo.configs/openejb-deployer/1.2-r465304/
car started in .302s
Module 15/22 org.apache.geronimo.configs/client-deployer/1.2-r465304/
car started in .067s
Module 16/22 org.apache.geronimo.configs/axis-deployer/1.2-r465304/
car started in .585s
Module 17/22 org.apache.geronimo.configs/sharedlib/1.2-r465304/
car started in .007s
Module 18/22 org.apache.geronimo.configs/jetty-deployer/1.2-r465304/
car started in .259s
Module 19/22 org.apache.geronimo.configs/welcome-jetty/1.2-r465304/
car started in .452s
Module 20/22 org.apache.geronimo.configs/webconsole-jetty/1.2-r465304/
car started in 27.210s
Module 21/22 org.apache.geronimo.configs/remote-deploy-jetty/1.2-
r465304/car started in .190s
Module 22/22 org.apache.geronimo.configs/hot-deployer/1.2-r465304/
car started in .278s
And from 1.1 jetty;
Booting Geronimo Kernel (in Java 1.4.2_09)...
Module 1/20 geronimo/rmi-naming/1.1.1/car started in .
206s
Module 2/20 geronimo/j2ee-server/1.1.1/car started in .
350s
Module 3/20 geronimo/j2ee-security/1.1.1/car started in .
339s
Module 4/20 geronimo/axis/1.1.1/car started in .
049s
Module 5/20 geronimo/openejb/1.1.1/car started in .
232s
Module 6/20 geronimo/system-database/1.1.1/car started in
1.521s
Module 7/20 geronimo/activemq-broker/1.1.1/car started in .
810s
Module 8/20 geronimo/activemq/1.1.1/car started in .
218s
Module 9/20 geronimo/jetty/1.1.1/car started in .
445s
Module 10/20 geronimo/geronimo-gbean-deployer/1.1.1/car started in .
180s
Module 11/20 geronimo/j2ee-deployer/1.1.1/car started in .
163s
Module 12/20 geronimo/openejb-deployer/1.1.1/car started in .
187s
Module 13/20 geronimo/client-deployer/1.1.1/car started in .
036s
Module 14/20 geronimo/axis-deployer/1.1.1/car started in .
050s
Module 15/20 geronimo/sharedlib/1.1.1/car started in .
005s
Module 16/20 geronimo/jetty-deployer/1.1.1/car started in .
181s
Module 17/20 geronimo/welcome-jetty/1.1.1/car started in .
441s
Module 18/20 geronimo/webconsole-jetty/1.1.1/car started in
7.797s
Module 19/20 geronimo/remote-deploy-jetty/1.1.1/car started in .
165s
Module 20/20 geronimo/hot-deployer/1.1.1/car started in .
220s
And tomcat 1.2
Module 1/22 org.apache.geronimo.configs/rmi-naming/1.2-r465304/
car started in .282s
Module 2/22 org.apache.geronimo.configs/j2ee-server/1.2-r465304/
car started in .142s
Module 3/22 org.apache.geronimo.configs/transaction/1.2-r465304/
car started in .212s
Module 4/22 org.apache.geronimo.configs/j2ee-security/1.2-r465304/
car started in .325s
Module 5/22 org.apache.geronimo.configs/axis/1.2-r465304/
car started in .044s
Module 6/22 org.apache.geronimo.configs/openejb/1.2-r465304/
car started in 2.236s
Module 7/22 org.apache.geronimo.configs/system-database/1.2-r465304/
car started in .000s
Module 8/22 org.apache.geronimo.configs/activemq-broker/1.2-r465304/
car started in 1.155s
Module 9/22 org.apache.geronimo.configs/activemq/1.2-r465304/
car started in .239s
Module 10/22 org.apache.geronimo.configs/tomcat/1.2-r465304/
car started in 1.588s
Module 11/22 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2-
r465304/car started in .292s
Module 12/22 org.apache.geronimo.configs/j2ee-deployer/1.2-r465304/
car started in .206s
Module 13/22 org.apache.geronimo.configs/connector-deployer/1.2-
r465304/car started in .131s
Module 14/22 org.apache.geronimo.configs/openejb-deployer/1.2-r465304/
car started in .306s
Module 15/22 org.apache.geronimo.configs/client-deployer/1.2-r465304/
car started in .066s
Module 16/22 org.apache.geronimo.configs/axis-deployer/1.2-r465304/
car started in .492s
Module 17/22 org.apache.geronimo.configs/sharedlib/1.2-r465304/
car started in .007s
Module 18/22 org.apache.geronimo.configs/tomcat-deployer/1.2-r465304/
car started in .087s
Module 19/22 org.apache.geronimo.configs/welcome-tomcat/1.2-r465304/
car started in .204s
Module 20/22 org.apache.geronimo.configs/webconsole-tomcat/1.2-
r465304/car started in 4.658s
Module 21/22 org.apache.geronimo.configs/remote-deploy-tomcat/1.2-
r465304/car started in .373s
Module 22/22 org.apache.geronimo.configs/hot-deployer/1.2-r465304/
car started in .260s
Re: Weekly: Geronimo 1.2-r465304
Posted by Kevan Miller <ke...@gmail.com>.
On Oct 19, 2006, at 2:27 PM, Aaron Mulder wrote:
> 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.
Agreed that some optimization would be nice. However, this isn't
really a case of "optimization", I think. Something has changed quite
drastically between 1.1.1 and 1.2-SNAPSHOT. We've more than doubled
our startup time...
--kevan
Re: Weekly: Geronimo 1.2-r465304
Posted by Dain Sundstrom <da...@iq80.com>.
On Oct 19, 2006, at 11:27 AM, Aaron Mulder wrote:
> 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.
I've timed it before. Starting each gbean takes a very very long
time. I'd also guess that as you add more gbeans it gets slower. If
I had to bet, I'd blame AbstractName and AbstractNameQuery. When we
used object names we indexed the names so queries were faster, and
now we do a liner compare for each life-cycle event fired.
-dain
Re: Weekly: Geronimo 1.2-r465304
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
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 <gn...@gmail.com> 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 <ke...@gmail.com> 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
>
Re: Weekly: Geronimo 1.2-r465304
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <ke...@gmail.com> 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
Re: Weekly: Geronimo 1.2-r465304
Posted by Dain Sundstrom <da...@iq80.com>.
On Oct 19, 2006, at 12:22 PM, Kevan Miller wrote:
> On Oct 19, 2006, at 2:01 PM, Dain Sundstrom wrote:
>
>> I'm using Java 1.4.2_09.
>
> Me too. :-)
>
> 'java -jar server.jar' on 1.4.2 works for me.
>
> './geronimo.sh run' on 1.4.2 does not work for me
>
> './geronimo.sh run' on 1.5 works for me.
>
geronimo.sh run works for me in Java 1.4
$ geronimo-jetty-j2ee-1.2-r465304/bin/geronimo.sh run
Using GERONIMO_BASE: /Users/dain/t/geronimo-jetty-j2ee-1.2-r465304
Using GERONIMO_HOME: /Users/dain/t/geronimo-jetty-j2ee-1.2-r465304
Using GERONIMO_TMPDIR: /Users/dain/t/geronimo-jetty-j2ee-1.2-r465304/
var/temp
Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/
Versions/CurrentJDK/Home
Booting Geronimo Kernel (in Java 1.4.2_09)...
Starting Geronimo Application Server v1.2-r465304
[************************] 100% 39s Startup complete
-dain
Re: Weekly: Geronimo 1.2-r465304
Posted by Kevan Miller <ke...@gmail.com>.
On Oct 19, 2006, at 2:01 PM, Dain Sundstrom wrote:
>
> I'm using Java 1.4.2_09.
Me too. :-)
'java -jar server.jar' on 1.4.2 works for me.
'./geronimo.sh run' on 1.4.2 does not work for me
'./geronimo.sh run' on 1.5 works for me.
--kevan
Re: Weekly: Geronimo 1.2-r465304
Posted by Dain Sundstrom <da...@iq80.com>.
On Oct 19, 2006, at 10:53 AM, Kevan Miller 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?
I'm using Java 1.4.2_09.
-dain
Re: Weekly: Geronimo 1.2-r465304
Posted by Kevan Miller <ke...@gmail.com>.
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
Re: Weekly: Geronimo 1.2-r465304
Posted by Dain Sundstrom <da...@iq80.com>.
On Oct 19, 2006, at 9:22 AM, Dain Sundstrom wrote:
> On Oct 18, 2006, at 6:59 PM, Kevan Miller wrote:
>
>>
>> On Oct 18, 2006, at 5:19 PM, Dain Sundstrom wrote:
>>
>>> Geronimo 1.2-r465304 - Oct 18, 2006
>>>
>>> http://people.apache.org/dist/geronimo/unstable/1.2-r465304/
>>>
>> ...
>>> NOTE: This build is not an official release, nor tested, and
>>> should be
>>> considered unstable.
>>
>> Dain,
>> The jetty-j2ee server does not start for me. Does it work for you?
>
> I test started all of the binaries before uploading, but I'll
> download geronimo-jetty-j2ee-1.2-r465304.tar.gz and try to start it.
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
Geronimo Application Server started
-dain
Re: Weekly: Geronimo 1.2-r465304
Posted by Dain Sundstrom <da...@iq80.com>.
On Oct 18, 2006, at 6:59 PM, Kevan Miller wrote:
>
> On Oct 18, 2006, at 5:19 PM, Dain Sundstrom wrote:
>
>> Geronimo 1.2-r465304 - Oct 18, 2006
>>
>> http://people.apache.org/dist/geronimo/unstable/1.2-r465304/
>>
> ...
>> NOTE: This build is not an official release, nor tested, and
>> should be
>> considered unstable.
>
> Dain,
> The jetty-j2ee server does not start for me. Does it work for you?
I test started all of the binaries before uploading, but I'll
download geronimo-jetty-j2ee-1.2-r465304.tar.gz and try to start it.
-dain
Re: Weekly: Geronimo 1.2-r465304
Posted by Kevan Miller <ke...@gmail.com>.
On Oct 18, 2006, at 5:19 PM, Dain Sundstrom wrote:
> Geronimo 1.2-r465304 - Oct 18, 2006
>
> http://people.apache.org/dist/geronimo/unstable/1.2-r465304/
>
...
> NOTE: This build is not an official release, nor tested, and should be
> considered unstable.
Dain,
The jetty-j2ee server does not start for me. Does it work for you?
--kevan