Tamer,
If you really want to run jetty on port 80, I would suggest using the
iptables technique[1]. I used it before and it's pretty easy to get
working and doesn't require jetty to run as root.
Tim
[1] http://docs.codehaus.org/display/JETTY/port80
On Wed, Feb 17, 2010 at 11:25 AM, Jim Barrows
On Wed, Feb 17, 2010 at 10:08 AM, Tamer Rizk wrote:
> I am using Apache as a reverse proxy forwarding traffic to Jetty on port
> 8181. I am under the impression that a slight performance benefit offered by
> Apache would be offset by the bottleneck arising from double request
> handling (resultin
I am using Apache as a reverse proxy forwarding traffic to Jetty on port
8181. I am under the impression that a slight performance benefit offered by
Apache would be offset by the bottleneck arising from double request
handling (resulting in a reduction of throughput in comparison to direct
request
I would recommend using Nginx or similar up front and using a reverse proxy
setup - it is the most optiomal solution as Nginx can handle a vast number more
connections than Jetty so it makes scaling your app easier on a single machine.
Cheers, Tim
On 17 Feb 2010, at 15:11, Jeppe Nejsum Madsen
On Wed, Feb 17, 2010 at 4:07 PM, Jeppe Nejsum Madsen wrote:
> On Wed, Feb 17, 2010 at 3:40 PM, trizk wrote:
Ok, just reread your post and saw you want to run Jetty on port 80.
I've not tried this,I usually run a frontend (such as nginx) in front.
Not sure how the different distros support this o
On Wed, Feb 17, 2010 at 3:40 PM, trizk wrote:
> When i run mvn -e jetty:run in helloworld, it dies with
>
> java.lang.ClassNotFoundException: org.mortbay.setuid.SetUIDServer
>
> Has anyone had any success running the Jetty plugin as a non-root user
> for their Lift web applications? I realize tha
I am kicking the tires on Lift on an experimental server. I have a
problem while trying to configure Jetty to run as a non-root user for
security purposes. I have followed the instructions at
http://docs.codehaus.org/display/JETTY/port80 for building libsetuid
and the following is now located in /
