Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: July 24, 2005 7:46 AM
To: Tomcat Users List
Subject: Re: Error 500 messages
The response is being comitted before the erro is being thrown. You need to
set the buffer size to be larger. Its a page directive.
-Tim
Adile Abbadi wrote
7:46 AM
To: Tomcat Users List
Subject: Re: Error 500 messages
The response is being comitted before the erro is being thrown. You need to
set the buffer size to be larger. Its a page directive.
-Tim
Adile Abbadi wrote:
Hi Tim,
Thank you very much - that has helped - however I discovered
Adile
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: July 22, 2005 12:42 PM
To: Tomcat Users List
Subject: Re: Error 500 messages
flush=false
-Tim
Adile Abbadi wrote:
Hi Tim,
Thanx for the information - I forgot about that. I guess the question is
why
did
Subject: RE: Error 500 messages
Hi Adile,
I did say it was untested, and I've spotted a problem in my code already
(why are bugs so invisible BEFORE you press the send button??!!)
On 22 Jul 2005 at 9:41, Rob Hills wrote:
Something like the following (untested) in your error.jsp should do the
trick
This line jsp:include page=top.html flush=true will commit the response
and send html back to the client. Once that is done - no error messages will
be sent back to the client and you will end up with a blank screen.
-Tim
Adile Abbadi wrote:
Hi Rob,
Thanx for this - this is great - I may
Users List
Subject: Re: Error 500 messages
This line jsp:include page=top.html flush=true will commit the
response
and send html back to the client. Once that is done - no error messages will
be sent back to the client and you will end up with a blank screen.
-Tim
Adile Abbadi wrote:
Hi Rob
]
Sent: July 22, 2005 12:20 PM
To: Tomcat Users List
Subject: Re: Error 500 messages
This line jsp:include page=top.html flush=true will commit the
response
and send html back to the client. Once that is done - no error messages will
be sent back to the client and you will end up with a blank screen
still get a blank page - however if I remove the includes within the
include then the exception is visible. Any ideas on this?
Cheers
Adile
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: July 22, 2005 12:42 PM
To: Tomcat Users List
Subject: Re: Error 500 messages
Hi
all,
I've got a very
simple question to ask and I'm sure someone out there can help me. Ok I just
migrated from Tomcat 3 to Tomcat 4 and everything is working great except one
little thing. But a little background before I go on.
Apache/Tomcat4
configuration - using libapache-mod_jk
It might be easier than you think to output the error right onto the
page itself.
But would it help if you see the errors (+ other things) on the tomcat
console?? It will certainly help in your debugging.
To do that edit the server.xml in the conf directory and remove lines
similar to this:
To: Tomcat Users List
Subject: Re: Error 500 messages
It might be easier than you think to output the error right onto the
page itself.
But would it help if you see the errors (+ other things) on the tomcat
console?? It will certainly help in your debugging.
To do that edit the server.xml
Hi Adile,
On 21 Jul 2005 at 19:09, Adile Abbadi wrote:
Now I did a little more experimenting and discovered something interesting -
as I said I can get an exception to be thrown to the page in a simple JSP
file (I made it do a null pointer for example) and I can get it do pretty
any other
Hi Adile,
I did say it was untested, and I've spotted a problem in my code already
(why are bugs so invisible BEFORE you press the send button??!!)
On 22 Jul 2005 at 9:41, Rob Hills wrote:
Something like the following (untested) in your error.jsp should do the trick:
%
if (exception ==
13 matches
Mail list logo
