Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 84009 invoked from network); 28 Mar 2005 01:55:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Mar 2005 01:55:15 -0000 Received: (qmail 12157 invoked by uid 500); 28 Mar 2005 01:54:56 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 12140 invoked by uid 500); 28 Mar 2005 01:54:56 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 12126 invoked by uid 99); 28 Mar 2005 01:54:56 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of paul@mnwebhost.net designates 207.67.28.253 as permitted sender) Received: from smtp1.mnwebhost.net (HELO smtp1.mnwebhost.net) (207.67.28.253) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 27 Mar 2005 17:54:54 -0800 X-AuthUser: paul@mnwebhost.net Received: from [127.0.0.1] (66.41.12.150:3792) by mnwebhost.net with [XMail 1.18 (Win32/Ix86) ESMTP Server] id for from ; Sun, 27 Mar 2005 19:56:50 -0600 Message-ID: <424763ED.8000302@mnwebhost.net> Date: Sun, 27 Mar 2005 19:54:53 -0600 From: Paul User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Address localhost:8080 already in use References: <689DE60AFD3D1C45B7F20A2AF8D8D7E901761BDF@hydra.rws.local> In-Reply-To: <689DE60AFD3D1C45B7F20A2AF8D8D7E901761BDF@hydra.rws.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I ran into this issue a while ago when I wrote a cronjob to check that tomcat is outputting something expected and if not, stopping & re-starting the service. However, since my tomcat checking script (the cronjob) was running every minute, I did run into some occasions where the startup script would be called twice before tomcat was fully up and responding to requests. Probably the same thing you're reporting. If you only run one instance of tomcat, then you should be ok simply doing a "killall java". However, if you are running multiple instances of tomcat, then you only want to kill the suspected instance of tomcat and not all of them. If you're running all instances from the same install dir, then look for something unique in "ps -ef" or you can adjust your CATALINA_OPTS in catalina.sh so that you can tell which instance is which when you run "ps -ef" then only kill those processes. If you're running them from different install directories, then just grep the output of "ps -ef" see the ones running from that path. A simple shell script can automate that for you. Regards, -Paul Fredrik Liden wrote: >Here is a big problem that I've run into so many times. >I run start tomcat. >And then by accident I start it again while it is running. >After that I can't shut it down again. And if I try to run it it says >the address is in use. Have someone found any solution to this problem? > >Any suggestions would be appreciated. > >/Fredrik > >--------------------------------------------------------------------- >To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org