Len Popp wrote:
JasperException is a subclass of Exception, so you should be able to
use the usual Exception methods on it. But it's not a
NullPointerException. JasperException is what I get if I mess up the
syntax in a JSP page. So, check for that.
--
Len
Actually, JasperException extends fr
Sorry, there was a thread about jsp errors, but i thought this was
different enough to warrant a new thread.
I'm having trouble programatically retrieving the root cause of a JSP
Exception. Basically, if a NullPointerException is thrown on a JSP page,
I want to know that this exception was thr
Len Popp wrote:
You can use an directive in web.xml to send uncaucht
exceptions to an error page:
java.lang.Exception
/error
Thanks Len, but I want to do more than catch them, I want to also report
on them -- is the exception accessible on the resulting page?
Glen Mazza wrote:
And another is to define the error page in your web.xml:
500
/myPage.jsp
I would save these for generic HTTP error codes, or generic Java
exceptions (NullPointerErrors, ClassCastExceptions, perhaps), things are
more likely the result of errors in coding than
I am on Tomcat 5.0.x
I am familiar with a couple ways to capture errors that occur on the JSP
side. One way is to use the error page tag:
<%@ page errorPage="MyErrorPage.jsp" %>
And another is to define the error page in your web.xml:
500
/myPage.jsp
I've inherited a vast
I recently added some settings to my worker.properties which caused
apache to throw occassional "503" ("Service Temporarily Unavailable")
errors. I've commented out the setting and the errors do not occur.
The settings are related to timeouts (connect_timeout, prepost_timeout,
and reply_timeout)
Duan, Nick wrote:
Apparently mod_jk does support several load balancing algorithms other
than round-robin. You may want to set the "method" property of load
balancer to Request or Traffic. See instructions on worker properties
for details.
http://tomcat.apache.org/connectors-doc/config/workers
Mladen Turk wrote:
Yes, use the 'Advanced worker directives'
http://tomcat.apache.org/connectors-doc/config/workers.html
The connect_timeout, prepost_timeout and reply_timeout are meant to
be used with hanged or very busy backend (Tomcat) servers.
Thanks.
I'm having trouble understanding the
I was wondering if I could get some advice on better failover for my
current setup. I'm using mod_jk 1.2.14 with Tomcat 5.0.28.
One issue that we occassionally run across is that an instance of tomcat
will become unresponsive (due to out of memory errors for example) but
mod_jk will still rout
