Typically an error like this would show in the catalina.out log file.  I 
would suspect though that you are experiencing a seg fault in the jvm on 
startup.  At the very minimum, if TC 4 is starting successfully, you should 
see a number of java threads in the output of 'ps -A'.

--David

On Monday 18 February 2002 04:09 pm, you wrote:
> Redhat Linux 7.2 (with latest updates)
> Sun JDK 1.4.0 Final
> Apache 1.3
> Tomcat 4_0_2 ***RPM Version***
>
> I had a working copy of Tomcat 4_0_1 until this morning.
>
> I downloaded the new 4_0_2 RPMs and installed them as indicated in
> RUNNING.txt.
>
> When I attempt to start the Tomcat Process, the startup script seems to
> execute fine.  However, a ps -A indicates that no Java process is running.
> When I execute the tomcat4 stop command, I receive a series of Java error
> messages:
> Catalina.stop:java.net.ConnectionException: Connection refused.
> ...
> BootStrap.java: 243
>
> I have combed through my configuration and everything seems OK.  I ran
> netstat and do not see any conflicting ports.  I did not touch the
> server.xml file.  I, however, do not see the reference to port 8080 that
> used to be in older versions of server.xml.
>
> I checked my java.policy and catalina.policy files and they seem OK.  I did
> note that the java.policy file allows listen for ports above 1024.  This
> was OK with prior versions, and I do not see any documentation indicating
> otherwise.  Changing to connect does not help.
>
> Any advice is greatly appreciated.
>
> Can anyone assist or offer any advice.
>
>
>
>
> Shannon Brown
>   Internet Technologies Architect
>   Business Technologies Advisor
>     www.shannonbrown.net
>     [EMAIL PROTECTED]
>     717.665.5656

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to