Jetty and Port 80

Frank,

Could provide me with some details on how your enabled/configured mod_proxy
for Apache?

Thanks,
David

> Message: 5
> From: "Frank Morton" <fmorton@xxxxxxxxxxxx>
> To: <jboss-user@xxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: [JBoss-user] Jetty and Port 80
> Date: Mon, 8 Jul 2002 10:06:14 -0500
> Reply-To: jboss-user@xxxxxxxxxxxxxxxxxxxxx
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_001F_01C22667.1839E6D0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> I just use apache's mod_proxy to redirect.
>   I'm obviously a newbie to JBoss/Jetty.  Excuse me if this post=20
>   would be better posted elsewhere but I would greatly appreciate=20
>   any thoughts on the following problem:
>
>   I'm running Redhat 7.2 which has IPCHAINS enabled by default. I've
>   tried the suggestions for redirecting traffic=20
>   (http://jetty.mortbay.com/jetty/doc/User80.html) as follows:
>
>   /sbin/ipchains -I input --proto TCP --dport 80 -j REDIRECT 8080
>
>   or:
>
>   /sbin/iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT
>   --to-port 8080
>
>   The IPCHAINS option doesn't work apparently because kernel is NOT
>   compiled with CONFIG_IP_MASQUERADE? I don't think I want to recompile
>   a kernel...sounds pretty heavy duty.
>
>   The IPTABLES option didn't work either, I'm getting the following
>   error when running iptables:
>
>   [root@xxxx webadmin]# /sbin/iptables -L
>   /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o:
>   init_module: Device or resource busy
>   Hint: insmod errors can be caused by incorrect module parameters,
>   including invalid IO or IRQ parameters
>   /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o: insmod
>   /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o failed
>   /lib/modules/2.4.9-34/kernel/net/ipv4/netfilter/ip_tables.o: insmod
>   ip_tables failed
>   iptables v1.2.4: can't initialize iptables table `filter': iptables
>   who? (do you need to insmod?)
>   Perhaps iptables or your kernel needs to be upgraded.
>
>   Does anybody have any suggestions to get these options to work or
>   another method to have Jetty/JBoss listen on port 80?
>
>   It seems to me this is a basic functionality that would be used =
> extensively=20
>   or are people out there using other methods for directing their =
> standard
>   port 80 traffic to JBoss/Jetty on port 8080?
>
>
>   Thanks,
>   David Sica
>   davidwsica@xxxxxxxxxxx
>


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf