Hi Christopher Schultz,
I understand that during a webapp reload, Tomcat will issue a 503 response.
The issue is that, I have named my war file as ROOT.war, so that, when I
access my tomcat default page using http://localhost:8080/ i get my
application's index page. This is how our out side server's tomcat is
configured.
You might be able to catch this at the Tomcat level and display
a certain "please wait" page.
I catch this 503 page from my tomcat/conf/web.xml file and place my
503.htmlin ROOT folder itself. Why, because tomcat looks for the
resources in this
folder. below is the snippet I used in my
tomcat/conf/web.xml file.
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<error-page>
<error-code>404</error-code>
<location>/error404.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/error404.jsp</location>
</error-page>
<error-page>
<error-code>503</error-code>
<location>/error404.jsp</location>
</error-page>
When I reload my application, that is ROOT.war form manager/html and at the
same time access the application in a different browser, tomcat gives blank
page.
Since ROOT it self is reloading, even though it has the files tomcat is not
fetching them.
If I remove the "/" from the <location> tab (so that I can specify a
different location) tomcat is not openning my application . It returns default
404 page for any URL I type.
>I do this using the ErrorDocument directive
available through Apache httpd.
There is no apache web server for our application. We only use tomcat 5.5.12.
I only want to know if using Apache is the only option for me.
Please tell me if There is any solution for this with in Tomcat.
Thanks and regards:
A. Quayum Sagri
On 5/18/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Abdul,
Abdul Qayyum wrote:
> Will this approach redirect the page to other when one is under
> reloading or upgration?
IIRC, during a webapp reload, Tomcat will issue a 503 response. You
might be able to catch this at the Tomcat level and display a certain
"please wait" page. I do this using the ErrorDocument directive
available through Apache httpd.
> The situation is that, we want to send a customised error page when our
> website is under upgration. It will approximately take 1 hour for
uploading
> a new war file on our server. During this time I want to show some
custom
> page.
Might I suggest that you upload your WAR file and /then/ deploy it? I'm
not sure how Tomcat does how upgrades (I hope it's smart enough to wait
until the WAR is fully uploaded to reload the webapp), but an hour of
down time is a /lot/. If all you're waiting for is the WAR file to
upload, then you do not need this additional downtime, and should avoid
it if possible.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGTZ/r9CaO5/Lv0PARAp2VAJ0Z85eclykwIGie8zcWqUvtvJ7GQQCgnuPl
j0UecbcpBzDR+L0wxcnyrtA=
=ZzR4
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
