Http_2.0.48 + Tomcat 4.1.29 + mod_jk2

Hi,
I use Http 2.0.48 + Tomcat 4.1.29 + mod_jk2 2.0.2
The problem to solve is: Send the user a self defined html-page in case of
Tomcat is down.

The ErrorDocument Directive in httpd.conf dosn't function. I get a Internal
Server Error with "Additionally, a 500 Internal Server Error error was
encountered while trying to use an ErrorDocument to handle the request."
in httpd.conf:
ErrorDocument 500 /myerrorpage.html

To catch the Error-message with Output Filter (ExtFilterDefine mode=output
....) dosn't function: This point will never reached.

The noWorkerMsg Directive in workers2.properties dosn't function. I get an
Error: "config.setAttribute() Error setting lb:lb noWorkerMsg"
in workers2.properties:
[lb:lb]
info=default load balancer
debug=0
noWorkerMsg=/myerrorpage.html
noWorkerCode=500

I read the Archives well, but there are only the same questions, but no
answers. Anybody know a solution? Please, I need a solution that the _user_
_never_ _get_ _a_ _white_ _page_ _with_ _error-message_ (if Tomcat is down
but apache is up), but always a "real" page, maybe the entrance-point .

Andy

Have you had any luck with this problem? I am struggling with the same

problem right now.

I want to use this directive:

ErrorDocument 500 /pderror/pd500.html

So I defined pderror with an alias

Alias /pderror/ "/var/.../efiles/"

I know this is okay b/c it will work for 404 and display my page:

ErrorDocument 404 /pderror/pd500.html

I can also use the directive to add simple text to the error page:

ErrorDocument 500 "I have a problem"

But "ErrorDocument 500 /pderror/pd500.html" fails with the message:

Additionally, a 500 Internal Server Error error was encountered while

trying to use an ErrorDocument to handle the request.

Please let me know if you have made any progress or learned that this

is insurmountable. brian aatt publicdialog ddoott net

Thanks,

Brian



"Andy" <egal@dev.null> wrote in message news:40220a5c$1@news.fhg.de...
> Hi,
> I use Http 2.0.48 + Tomcat 4.1.29 + mod_jk2 2.0.2
> The problem to solve is: Send the user a self defined html-page in case of
> Tomcat is down.
>
> The ErrorDocument Directive in httpd.conf dosn't function. I get a
Internal
> Server Error with "Additionally, a 500 Internal Server Error error was
> encountered while trying to use an ErrorDocument to handle the request."
> in httpd.conf:
> ErrorDocument 500 /myerrorpage.html
>
> To catch the Error-message with Output Filter (ExtFilterDefine mode=output
> ...) dosn't function: This point will never reached.
>
> The noWorkerMsg Directive in workers2.properties dosn't function. I get an
> Error: "config.setAttribute() Error setting lb:lb noWorkerMsg"
> in workers2.properties:
> [lb:lb]
> info=default load balancer
> debug=0
> noWorkerMsg=/myerrorpage.html
> noWorkerCode=500
>
> I read the Archives well, but there are only the same questions, but no
> answers. Anybody know a solution? Please, I need a solution that the
_user_
> _never_ _get_ _a_ _white_ _page_ _with_ _error-message_ (if Tomcat is down
> but apache is up), but always a "real" page, maybe the entrance-point .
>
> Andy
>
>
>

Here is one solution:

Use Apache's ability to add text to the error message, and instead of using
text, add a redirect in a script tag:

ErrorDocument 500 "<script>document.location='/path/err500.html';</script>"

This will replace the Apache error page with your html page. However, the
url will be changed, so hitting reload will not attempt to use the original
url to tomcat.

I will use this solution, and add some javascript to periodically attempt to
reload the original page. Of course this solution will fail if the browser
has disabled javascript.

Please let me know if there is a better solution.

Brian


"John Smith" <john@smiht.com> wrote in message
news:0Z9Wb.22217$7R.19335@newssvr27.news.prodigy.c om...
> Have you had any luck with this problem? I am struggling with the same
>
> problem right now.
>
> I want to use this directive:
>
> ErrorDocument 500 /pderror/pd500.html
>
> So I defined pderror with an alias
>
> Alias /pderror/ "/var/.../efiles/"
>
> I know this is okay b/c it will work for 404 and display my page:
>
> ErrorDocument 404 /pderror/pd500.html
>
> I can also use the directive to add simple text to the error page:
>
> ErrorDocument 500 "I have a problem"
>
> But "ErrorDocument 500 /pderror/pd500.html" fails with the message:
>
> Additionally, a 500 Internal Server Error error was encountered while
>
> trying to use an ErrorDocument to handle the request.
>
> Please let me know if you have made any progress or learned that this
>
> is insurmountable. brian aatt publicdialog ddoott net
>
> Thanks,
>
> Brian
>
>
>
> "Andy" <egal@dev.null> wrote in message news:40220a5c$1@news.fhg.de...
> > Hi,
> > I use Http 2.0.48 + Tomcat 4.1.29 + mod_jk2 2.0.2
> > The problem to solve is: Send the user a self defined html-page in case
of
> > Tomcat is down.
> >
> > The ErrorDocument Directive in httpd.conf dosn't function. I get a
> Internal
> > Server Error with "Additionally, a 500 Internal Server Error error was
> > encountered while trying to use an ErrorDocument to handle the request."
> > in httpd.conf:
> > ErrorDocument 500 /myerrorpage.html
> >
> > To catch the Error-message with Output Filter (ExtFilterDefine
mode=output
> > ...) dosn't function: This point will never reached.
> >
> > The noWorkerMsg Directive in workers2.properties dosn't function. I get
an
> > Error: "config.setAttribute() Error setting lb:lb noWorkerMsg"
> > in workers2.properties:
> > [lb:lb]
> > info=default load balancer
> > debug=0
> > noWorkerMsg=/myerrorpage.html
> > noWorkerCode=500
> >
> > I read the Archives well, but there are only the same questions, but no
> > answers. Anybody know a solution? Please, I need a solution that the
> _user_
> > _never_ _get_ _a_ _white_ _page_ _with_ _error-message_ (if Tomcat is
down
> > but apache is up), but always a "real" page, maybe the entrance-point .
> >
> > Andy
> >
> >
> >
>
>