[Resin-interest] Can't start resin on port 80, but 8080 okay (as root)

2009-03-18 Thread Rick Mann
Resin-3.2.1 (built Fri, 17 Oct 2008 04:11:01 PDT) I can't seem to run resin on port 80. I can run it on 8080 just fine, but when I change the config file to "80", I get: Can't use JNI to listen to port '0.0.0.0:80' because JNI support has not been compiled I'm launching it as root, but I've

Re: [Resin-interest] Can't start resin on port 80, but 8080 okay (as root)

2009-03-18 Thread Daniel J. Doughty
Rick, I don't think resin is picking up the right interface to listen on. You may have to specify your hostname somewhere in the resin.conf. I have a clustered setup, so I don't think my config file will help you much. Dan Rick Mann wrote: > Resin-3.2.1 (built Fri, 17 Oct 2008 04:11:01 PDT)

Re: [Resin-interest] Can't start resin on port 80, but 8080 okay (as root)

2009-03-18 Thread Aaron Freeman
On many UNIX systems only the root user can bind to ports below 1024, with out some tricks. That's probably your situation since it works fine on port 8080 but not port 80. If you comment out the user-name section and run it as root, it works fine on port 80? Aaron Rick Mann wrote: > Resin-3

Re: [Resin-interest] Can't start resin on port 80, but 8080 okay (as root)

2009-03-18 Thread Rick Mann
It does; I tried that right after sending the original post. But I thought resin was set up to do the binding (launched as root) then run as a different user after that. On Mar 18, 2009, at 12:52:37, Aaron Freeman wrote: > On many UNIX systems only the root user can bind to ports below 1024,

[Resin-interest] Hessian changes from Resin 3.0.x-3.1.x-3.2.x

2009-03-18 Thread Rick Mann
Hi. I'm using HessianKit to connect to a resin/hessian server setup. I build and deploy against three different Resin installations. One runs a version of 3.0, another 3.1, and a third 3.2. In the 3.0 and 3.1 installations, variables of type java.util.Date ended up getting wrapped in a dicti