Re: tomcat dies in OS X

2001-03-26 Thread miles poindexter

What does your .out file say? It should be in your logs folder. In 
Tomcat 4.0, its called catalina.out. Not sure what its called in 
3.2.1. If I remember correctly, 3.2.1 would just print to the command 
line if there was an error. If you're not getting msgs there. Maybe 
Tomcat is never really getting started up. Since the msg you're 
receiving when you run the shutdown script is similar to what I would 
get if I accidently ran the shutdown.sh script when Tomcat was 
already shutdown. I would try 4.0beta.

- miles

I'm running tomcat 3.2.1 on Mac OS X and it seems to just die after I make
a request...here's a breakdown of the chain of events...

//-first I turn on tomcat 3.2.1

cripes% bin/startup.sh
Using classpath:
/Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper.
jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S
hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t
omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib
cripes% 2001-03-26 01:58:24 - ContextManager: Adding context Ctx(
/examples )
2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /admin )
Starting tomcat. Check logs/tomcat.log for error messages
2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /pa2 )
2001-03-26 01:58:24 - ContextManager: Adding context Ctx(  )
2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /test )
2001-03-26 01:58:25 - PoolTcpConnector: Starting HttpConnectionHandler on
8080
2001-03-26 01:58:25 - PoolTcpConnector: Starting Ajp12ConnectionHandler on
8007

//-then I make a request like:
http://localhost:8080/pa2/step1.jsp

//-this is what my browser tells me
Cannot Load Address
Temporarily unable to connect: Connection refused

//-then I attempt to shutdown tomcat 3.2.1 and this is what I get

cripes% bin/shutdown.sh
Using classpath:
/Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper.
jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S
hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t
omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib
Stop tomcat
java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
 at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
 at java.net.Socket.init(Socket.java:273)
 at java.net.Socket.init(Socket.java:100)
 at org.apache.tomcat.task.StopTomcat.execute(StopTomcat.java:104)
 at org.apache.tomcat.startup.Tomcat.stopTomcat(Tomcat.java:267)
 at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:174)
 at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
cripes%

//-please help!!

sandeep




tomcat dies in OS X

2001-03-25 Thread sandeep parikh

I'm running tomcat 3.2.1 on Mac OS X and it seems to just die after I make
a request...here's a breakdown of the chain of events...

//-first I turn on tomcat 3.2.1

cripes% bin/startup.sh
Using classpath:
/Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper.
jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S
hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t
omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib
cripes% 2001-03-26 01:58:24 - ContextManager: Adding context Ctx(
/examples )
2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /admin )
Starting tomcat. Check logs/tomcat.log for error messages 
2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /pa2 )
2001-03-26 01:58:24 - ContextManager: Adding context Ctx(  )
2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /test )
2001-03-26 01:58:25 - PoolTcpConnector: Starting HttpConnectionHandler on
8080
2001-03-26 01:58:25 - PoolTcpConnector: Starting Ajp12ConnectionHandler on
8007

//-then I make a request like:
http://localhost:8080/pa2/step1.jsp

//-this is what my browser tells me
Cannot Load Address
Temporarily unable to connect: Connection refused

//-then I attempt to shutdown tomcat 3.2.1 and this is what I get

cripes% bin/shutdown.sh
Using classpath:
/Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper.
jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S
hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t
omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib
Stop tomcat
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.init(Socket.java:273)
at java.net.Socket.init(Socket.java:100)
at org.apache.tomcat.task.StopTomcat.execute(StopTomcat.java:104)
at org.apache.tomcat.startup.Tomcat.stopTomcat(Tomcat.java:267)
at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:174)
at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
cripes%

//-please help!!

sandeep




RE: Tomcat dies on OS X

2001-03-23 Thread Steve Fyfe

It runs fine for me when I start it from a Terminal window using the Tomcat.sh script. 
I did make sure to define the TOMCAT_HOME and JAVA_HOME environment variables first. 
And I am using it with Apache, not standalone.

How did you get it started? What exactly did you get for a stack trace? You may need 
to enable more logging options to track down the problem.

Steve Fyfe
CNI Corporation
Milford New Hampshire

[EMAIL PROTECTED]
(603) 673-6600

-Original Message-
From:   [EMAIL PROTECTED] 
Sent:   Thursday, March 22, 2001 12:31 PM
To: [EMAIL PROTECTED]
Subject:Tomcat dies on OS X

I'm running tomcat 3.2.1. on Mac OS X Public Beta and after starting
tomcat up, it will suddenly die not respond...When I shut it down it
throws me some errors pertaining to the HttpConnectionHandler class.

When I try to startup again, it throws the same error.  If I change the
port number in server.xml and restart the whole problematic cycle starts
again.

I've narrowed down some specific behaviors like:
- when I start tomcat, I can access the main page at http://localhost:port
- context manager recognizes and sets the appropriate paths for my
  servlets and jsps
- when I try to access my servlets/jsps, tomcat suddenly does not respond
  and thats where the trouble starts...

if anyone has any insights or information about this behavior, pls let me
know...

// s a n d e e p
// [EMAIL PROTECTED]




Tomcat dies on OS X

2001-03-22 Thread sandeep parikh

I'm running tomcat 3.2.1. on Mac OS X Public Beta and after starting
tomcat up, it will suddenly die not respond...When I shut it down it
throws me some errors pertaining to the HttpConnectionHandler class.

When I try to startup again, it throws the same error.  If I change the
port number in server.xml and restart the whole problematic cycle starts
again.

I've narrowed down some specific behaviors like:
- when I start tomcat, I can access the main page at http://localhost:port
- context manager recognizes and sets the appropriate paths for my
  servlets and jsps
- when I try to access my servlets/jsps, tomcat suddenly does not respond
  and thats where the trouble starts...

if anyone has any insights or information about this behavior, pls let me
know...

// s a n d e e p
// [EMAIL PROTECTED]




Re: Tomcat dies on OS X

2001-03-22 Thread miles poindexter

Have you tried using 127.0.0.1:8080 instead of localhost:8080? I'm 
just throwing out ideas here.
BTW, are you using the default port 8080 or did you change it to use 
another port?
How is Tomcat finding your JVM? did you create a CLASSPATH var in 
your /etc/csh.cshrc file?
I had weird sluggish behavior with 3.2.1 running on OSX beta where 
Tomcat would seem to finish its work fairly quickly from what I was 
seeing at the prompt output, But my browser would just sit there 
waiting for the results.

I was also getting HotspotJVM fatal errors.
I'm now using Tomcat 4.0b1 and these problems have disappeared.
Hopefully OS X final will have a more stable JVM

- miles

I'm running tomcat 3.2.1. on Mac OS X Public Beta and after starting
tomcat up, it will suddenly die not respond...When I shut it down it
throws me some errors pertaining to the HttpConnectionHandler class.

When I try to startup again, it throws the same error.  If I change the
port number in server.xml and restart the whole problematic cycle starts
again.

I've narrowed down some specific behaviors like:
- when I start tomcat, I can access the main page at http://localhost:port
- context manager recognizes and sets the appropriate paths for my
   servlets and jsps
- when I try to access my servlets/jsps, tomcat suddenly does not respond
   and thats where the trouble starts...

if anyone has any insights or information about this behavior, pls let me
know...

// s a n d e e p
// [EMAIL PROTECTED]