Hello, I have exactly the same problem and could not find any solution so far.
This is an answer I got from the [jetty-support] mailing list:
----- Original Message -----
From: Greg Wilkins
To: email@example.com ; firstname.lastname@example.org
Sent: Wednesday, July 30, 2003 8:58 AM
Subject: Re: [jetty-support] JBoss/Jetty: Servlet Not Initialized
Unfortunately this is not possible with the standard
With standard Jetty, you could simply not start your listeners
until the contexts were configured.
You should probably raise your concern on jboss-dev - so that
they can see that users want this feature.
Greg Wilkins<email@example.com> Phone/fax: +44 7092063462
Mort Bay Consulting Australia and UK. http://www.mortbay.com
> I have a problem with Jetty running as a servlet container in JBoss
> (3.0.4). When I start the application server, the Jetty (JBossWeb)
> service is deployed and started before my web applications (servlets)
> get initialized. As soon as Jetty starts, it accepts client requests.
> But servlets are not initialized yet and I
> get "javax.servlet.UnavailableException: Servlet Not Initialized"
> Is it possible to configure Jetty/JBoss so that it will wait for all
> web apps to initialize first and then starts accepting incoming
> Thanks in advance
Has anyone found a solution for this problem?
Until your ideal solution surfaces, you might want to go w/ a Filter. Granted, it's not as elegant as a declarative type solution, but at least the "initialized" checks/flags would be cleanly separated in one place.