geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "toby cabot (JIRA)" <>
Subject [jira] Commented: (GERONIMO-645) geronimo/jetty doesn't respect web.xml load-on-startup order
Date Wed, 18 May 2005 16:04:54 GMT
     [ ]
toby cabot commented on GERONIMO-645:

I wrote on the dev list (this system was down):
I started looking at this but I think I've gone as far as I can
without some advice.  I started by modifying JettyModuleBuilder to
create the servlet gbeans in the order specified by the
load-on-startup elements, and that worked the first time I ran the
server.  But not the second time.  So I looked into it a little more
and found that the BasicDependencyManager stores the dependencies as a
set, so when GBeanInstanceState.startRecursive() gets the children (in
this case the servlets) to start there's no order to them.
So I'm at a loss for what to do.  Modifying the dependency manager to
use lists instead of sets seems pretty drastic (since some of the
methods return sets) but it would probably make the server start up
more predictably.  But I'm not sure that's enough to ensure that the
load-on-startup order is respected all the way through deployment and

David Jencks responded:
Certainly the simplest solution is to give JettyServletHolder a
Previous reference so they form a linked list and set this reference in
the builder so as to be consistent with and enforce the startup order.
The  JettyFilterMapping uses this idea...

> geronimo/jetty doesn't respect web.xml load-on-startup order
> ------------------------------------------------------------
>          Key: GERONIMO-645
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: web
>     Versions: 1.0-M4
>  Environment: Fedora Core release 2 (Tettnang)
> java version "1.4.2_05"
> geronimo svn code revision 169673
>     Reporter: toby cabot

> Geronimo doesn't appear to start servlets in the order specified by <load-on-startup>.
 I can't figure out how the order is determined, but if I modify the values in a couple of
<load-on-startup> elements to try to change the startup order they come up in the same
order as before.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message