You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mike Comb <mc...@softcoin.com> on 2001/10/29 21:17:11 UTC
Loadbalancing tomcat 4.0.1
Sorry if this has been asked already, but I couldn't find much in the
archives. Is there any way to loadbalance tomcat 4.0.1? I am currently
using 3.2 and loadbalancing works fine with mod_jk, but it looks like this
functionallity has been removed in 4.0 (session cookies no longer contain
the app server name)? If loadbalancing is still possible can someone
provide a reference to how it is supposed to be done.
Thanks,
-Mike
-------------------------------------------
Mike Comb
Lead Engineer
SoftCoin, Inc
mcomb@softcoin.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Loadbalancing tomcat 4.0.1
Posted by Remy Maucherat <rm...@home.com>.
> Sorry if this has been asked already, but I couldn't find much in the
> archives. Is there any way to loadbalance tomcat 4.0.1? I am currently
> using 3.2 and loadbalancing works fine with mod_jk, but it looks like this
> functionallity has been removed in 4.0 (session cookies no longer contain
> the app server name)? If loadbalancing is still possible can someone
> provide a reference to how it is supposed to be done.
Sorry, it's not implemented at the moment.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat 4.0.1 doing odd Exception handling
Posted by Dmitri Colebatch <di...@bigpond.net.au>.
If an Error is thrown, the catch (Exception) wont catch it. If all you
want to do is find out what is going on, then you could change the catch
(Exception) to catch (Throwable) and you should see something. *warning*
this is about the only thing worse than catch (Exception) imho, so dont
leave it in your code once your figured it out (o:
cheers
dim
On Tue, 30 Oct 2001, Rob Johnson wrote:
> I'm having an interesting problem with Tomcat 4.0.1:
>
> I run this line of code from within a servlet:
>
> try {
> System.out.println("1");
> Classloader.getSystemClassLoader().loadClass(classname);
> System.out.println("2");
> } catch (Exception e) {
> System.out.println("Executing catch block");
> } finally {
> System.out.println("Executing finally block");
> }
>
> The Classloader line of code causes some sort of error because '2' is never
> printed out, but the catch block isn't executed either - execution jumps
> straight to the
> finally block. I can't find anything unusual in the logs. Can anyone help?
>
> The test code works fine with Tomcat 3.
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Tomcat 4.0.1 doing odd Exception handling
Posted by Rob Johnson <ro...@rsjohnson.fsnet.co.uk>.
I'm having an interesting problem with Tomcat 4.0.1:
I run this line of code from within a servlet:
try {
System.out.println("1");
Classloader.getSystemClassLoader().loadClass(classname);
System.out.println("2");
} catch (Exception e) {
System.out.println("Executing catch block");
} finally {
System.out.println("Executing finally block");
}
The Classloader line of code causes some sort of error because '2' is never
printed out, but the catch block isn't executed either - execution jumps
straight to the
finally block. I can't find anything unusual in the logs. Can anyone help?
The test code works fine with Tomcat 3.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>