Re: Tomcat dies after starting

2010-09-02 Thread jan gestre
On Thu, Sep 2, 2010 at 10:52 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jan, > > On 9/2/2010 2:42 AM, jan gestre wrote: >> I'm the only user of this dedicated machine, it's not yet in >> production that's why I'm quite sure :). Even the init scripts logs >

RE: Tomcat dies after starting

2010-09-02 Thread Caldarale, Charles R
> From: jan gestre [mailto:ipcopper...@gmail.com] > Subject: Re: Tomcat dies after starting > I'm the only user of this dedicated machine, it's not yet in > production that's why I'm quite sure :). Even the init scripts logs > tells that Tomcat is started only

Re: Tomcat dies after starting

2010-09-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan, On 9/2/2010 2:42 AM, jan gestre wrote: > I'm the only user of this dedicated machine, it's not yet in > production that's why I'm quite sure :). Even the init scripts logs > tells that Tomcat is started only to find out that it's not actually > r

Re: Tomcat dies after starting

2010-09-01 Thread jan gestre
On Thu, Sep 2, 2010 at 2:09 PM, Wesley Acheson wrote: > This looks like you've got many instances started at once (at least the end > part of it does). Ensure that it is shut down fully before starting again. > Are you the only user on this machine or is it shared? Other users may have > the same

Re: Tomcat dies after starting

2010-09-01 Thread Wesley Acheson
This looks like you've got many instances started at once (at least the end part of it does). Ensure that it is shut down fully before starting again. Are you the only user on this machine or is it shared? Other users may have the same ports used for a given reason. Its intresting that the JK conne

Re: Tomcat dies after starting

2010-09-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan, On 9/1/2010 8:44 PM, jan gestre wrote: > Here's my server.xml file, pardon me but I don't know what stack trace > is. The is the "bottom" of the stack trace, from your original post: > at > org.apache.catalina.connector.MapperListener.d

Re: Tomcat dies after starting

2010-09-01 Thread jan gestre
On Wed, Sep 1, 2010 at 9:28 PM, Caldarale, Charles R wrote: >> From: Wesley Acheson [mailto:wesley.ache...@gmail.com] >> Subject: Re: Tomcat dies after starting > >> Can you put in the beginning of the stack trace? > > Nice that the OP cut off the critical information

Re: Tomcat dies after starting

2010-09-01 Thread jan gestre
On Wed, Sep 1, 2010 at 4:40 PM, Wesley Acheson wrote: > Can you put in the beginning of the stack trace? > > Some things to look at make sure that you have permission to bind to > the port that you've set your http connection to. (you probably won't > be able to bind to port 80 on a linux box) > >

RE: Tomcat dies after starting

2010-09-01 Thread Caldarale, Charles R
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com] > Subject: Re: Tomcat dies after starting > I know that. I was trying to keep it simple. The problem with making an unqualified statement is that many people - especially inexperienced ones - will take it as an absolute, res

Re: Tomcat dies after starting

2010-09-01 Thread Wesley Acheson
On Wed, Sep 1, 2010 at 3:28 PM, Caldarale, Charles R wrote: >> From: Wesley Acheson [mailto:wesley.ache...@gmail.com] >> Subject: Re: Tomcat dies after starting > > Of course you can - but you have to use the proper technique, such as > starting Tomcat via jsvc or using ip

RE: Tomcat dies after starting

2010-09-01 Thread Caldarale, Charles R
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com] > Subject: Re: Tomcat dies after starting > Can you put in the beginning of the stack trace? Nice that the OP cut off the critical information... Also, the OP should post the server.xml, preferably with comments removed and

Re: Tomcat dies after starting

2010-09-01 Thread Wesley Acheson
Can you put in the beginning of the stack trace? Some things to look at make sure that you have permission to bind to the port that you've set your http connection to. (you probably won't be able to bind to port 80 on a linux box) RHEL5 has selinux installed by default which may cause problems. I