You should be able to cause those requests to fail by setting read-timeout
and write-timeout
in <http>.  But it probably won't be a 503.

Be careful if you do decide to start a background thread from your servlet.
There was a recent thread on the mailing list about that.


On 2/8/07, Daniel López <[EMAIL PROTECTED]> wrote:


Not sure if that would work for you or not, but another option would be
to move that initial process to a background thread and then your app
can check itself if the init has finished or not, and answer with a
nicer message "initalisation in progress, please wait..." etc, rather
than holding the container initialisation for that long.

The problem I see with halting resin init-process is that if you add
other servlets or other applications in the same container, they might
have to wait for that long, even if they could be answering requests
already. Moreover, doing it on your own would also make your web app
container-agnostic, you would not depend on the container holding other
servlets or not, returning 503s or not...

Just an idea,

Bryan Engel escribió:
> Hi,
> I have a servlet running on Resin 3.0.14 that takes a very long in init
> (up to 15 minutes).  As soon as init has finished, all the requests that
> came in during that time are processed, even it they are minutes old.
> I tried using the following in my resin.conf file but this didn't do
> anything:
>  <web-app-default>
>       <active-wait-time>5s</active-wait-time>
>       ...
> Is there a way to make resin turn away these requests with 503s or
> similar until init is finished?
> Thanks in advance.

resin-interest mailing list

resin-interest mailing list

Reply via email to