If I understand the problem correctly it may be apache redirecting to
the 404 error page when it cannot communicate with the connector to
JBoss - I have not used JBoss in a long time.
The solution might be to modify apache's http.conf file to use the
ErrorDocument redirect feature of Apache.
Simply add the following to the apache http.conf either in the virtual
host area or to the general setting section of the config file.
For Example:
ErrorDocument 404
/errors/missing.html
ErrorDocument 500 /errors/server_down.html
(Regards to Princess Leia :) )
Scott
[EMAIL PROTECTED] wrote:
Can I step out of the box first? What version of JBoss
are you using? In recent versions tomcat doesn't start listening until
all applications are fully deployed.
Anyhow, IIRC this is the problem with mod_proxy. Since it successfully
served up the request....you get success and it swallows the 404. you
could probably do some funk with mod_rewrite but I stay away from the
evil that is mod_rewrite. If all this is a problem then you're best
using mod_jk 1.2 -->8009 or skipping apache and using iptables
8080->80 or the very lovely (assuming linux):
http://www.olafdietsche.de/linux/accessfs/ and running jboss on 80 but
as a normal user!
-Andy
David Cooper wrote:
Ok, all you jboss experts out there:
I have Apache talking to jboss. At times I have to restart the jboss
server
or redeploy an ear file. Until the deployment is complete jBoss
reports a
404 error for the url associated with the application, e.g.
www.foo.bar/someApp goes to Apache gets forwarded to jboss via a
proxypass
at port 8080, jboss services the request, fails with a 404 error
because
someApp is not fully deployed yet and sends back a lovely SUCCESSFUL
html
response to Apache that contains all the 404 failure information that
jboss
spits out.
HOW DO I GET A PRETTY 404 ERROR BACK TO APACHE!!!!! I can't find the
right
configuration to intercept the 404 prior to deployment of someApp.
Once
someApp is fully deployed, the web.xml
<error-page><error-code>404</error-code>...</error-page>
works fine. The
time I'm worried about is the window when jboss is up and servicing
HTTP
requests but someApp is not fully deployed.
Help me Obi-Wan, your my only hope!
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
|
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
