Re: I'm more confused than ever about where STDOUT goes

Mark, Thanks for taking the time to look into the problem. I'll take your advice and do a new install. What should I see when I start Tomcat with 'catalina.bat run'? -=bill Mark Thomas wrote: Wm.A.Stafford wrote: Mark, 'catalina.bat' run does not r

Re: I'm more confused than ever about where STDOUT goes

Mark, 'catalina.bat' run does not return to the command line. It takes a ctrl/c to stop the process. -=bill Mark Thomas wrote: Wm.A.Stafford wrote: Mark, Thanks for taking an interest. I ran 'catalina.bat run' and got the following: C:\Program Files\Apache Softwa

Re: I'm more confused than ever about where STDOUT goes

or any advice, -=bill Mark Thomas wrote: Wm.A.Stafford wrote: First of all, thanks to Martin and Chuck for the replies to my original question about Tomcat 5.5 logging. To reiterate: I've installed Tomcat5.5.27 on Windows XP as a stand alone (not service) server and I do not see any of the

I'm more confused than ever about where STDOUT goes

First of all, thanks to Martin and Chuck for the replies to my original question about Tomcat 5.5 logging. To reiterate: I've installed Tomcat5.5.27 on Windows XP as a stand alone (not service) server and I do not see any of the logged info that I would expect when I start Tomcat. At the very

Tomcat 5.5 logging confusion

I am installing Tomcat 5.5.27 on Windows XP as the servlet container for a Spring MVC app we will be hosting. I have installed many older versions of Tomcat with no problems but I'm stuck on this installation. In older Tomat versions when an application is started, in my case a Spring based a

Tomcat hangs, what to do to diagnose the problem?

Our Tomcat 4.1.30 instance seems to hang about once a week. i.e. the application is unresponsive and it can not be restarted from the management console. Tomcat must be restarted to restore functionality. There is nothing in the logs to indicate explicitly what is going on. The only logging t

Re: Can two Tomcat web apps deadlock each other?

one app fails during startup. For unknown reasons Tomcat either does not get notified of the failure and is left some sort of waiting state or Tomcat gets hung trying to shutdown the failed app. Thanks again for replying, -=beeky Peter Crowther wrote: From: Wm.A.Stafford [mailto:[

Re: Can two Tomcat web apps deadlock each other?

check that your application shuts down cleanly - no exceptions are thrown during shutdown (but they should be logged) and preferably there are no finally() methods. Wm.A.Stafford wrote: Thanks Alexey. Unfortunately, the server in question is not ours and we do not even have log in on it, so a

Re: Can two Tomcat web apps deadlock each other?

acquired and what locks they are waiting for. - Alexey. Wm.A.Stafford wrote: We are deploying a newer version of a web app to run in the same Tomcat instance (1.4.31) as the existing version. On our development servers, winXP, if the new version encounters a startup problem the production app

Can two Tomcat web apps deadlock each other?

We are deploying a newer version of a web app to run in the same Tomcat instance (1.4.31) as the existing version. On our development servers, winXP, if the new version encounters a startup problem the production app will start and only the new version will fail. On the production server, wh

tomcat 1.4.31 hangs when app is deployed

We are running into a problem we have never seen before. Tomcat is hanging when restarted after a war file is deployed. In the past any problems resulted in Tomcat just not starting the app and there was usually a clear indication in a log file somewhere. Because a third party manages the