Re: Blocking AJP13 (port 8009) access

2006-02-14 Thread Antony Riley
Try adding address=127.0.0.1 to the ajp13 connector tag in server.xml, and configuring apache to connect to 127.0.0.1 if you haven't already. This should stop the ajp13 port from being visable to other machines. As far as iptables goes, you probably want -o lo -j ACCEPT at the top of the

Re: problems with Clusters or apache connector not sure which one

2006-02-13 Thread Antony Riley
I thought you said tomcat ran on 3 different boxes and it was a cluster ? java.io.IOException: Connection reset by peer This means that the tcp connection was severed somehow, this is typically caused by a firewall dropping idle TCP connections, or someone unplugging a network cable, or someone

Re: java.lang.Object cannot be resolved

2006-02-13 Thread Antony Riley
try as root: rpm -e `rpm -q -f /usr/bin/javac` Or something like that. Basically uninstall which ever pitiful excuse for java is installed on your system by default leaving only the sun jdk. Probably a good idea to check that nothing needs it before you do it. On that note, why do certain

Re: webapp under different URLs with different JSP but same java classes

2006-02-10 Thread Antony Riley
You could use a javax.servlet.Filter apparently, and say redirect requests to a particular servername to /jsp_a and redirect the rest to /jsp_b. basically installing a filter which does the following: public void doFilter(request,response,chain) { if(request.getServerName.equals(server1) {

Re: pure java mod_rewrite using javax.servlet.Filter

2006-02-10 Thread Antony Riley
is your friend there. Bruno Georges Glencore International AG Tel. +41 41 709 3204 Fax +41 41 709 3000 - Original Message - From: Antony Riley [EMAIL PROTECTED] Sent: 10.02.2006 14:32 To: users@tomcat.apache.org Subject: pure java mod_rewrite using javax.servlet.Filter Hiya all