geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: [jira] Created: (GERONIMO-645) geronimo/jetty doesn't respect web.xml load-on-startup order
Date Wed, 18 May 2005 02:00:12 GMT
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 and I admit I thought I had 
implemented it for servlet holder also :-(

david jencks
On May 17, 2005, at 1:04 PM, toby cabot wrote:

> On Wed, May 11, 2005 at 08:37:19PM +0200, toby cabot (JIRA) wrote:
>> Geronimo doesn't appear to start servlets in the order specified
>> by <load-on-startup>.
> 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
> startup.
> If anyone has any ideas I'd be happy to put some more legwork into
> this.
> Thanks,
> Toby
> PS.  Ordinarily I'd add comments like this to Jira but it's down:
> Proxy Error
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET 
> /jira/secure/BrowseProject.jspa.
> Reason: Error reading from remote server
> Apache/2.0.54 (Unix) mod_ssl/2.0.54 OpenSSL/0.9.7a DAV/2 SVN/1.2.0-dev 
> Server at Port 80

View raw message