Since the final release hasn't occurred yet, you will find the currrent 3.3.1 release (Release Candidate 1) under Milestone Builds, i.e.
<http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1-rc1/bin/> The nightly 3.3.x build is found under Nightly Builds, i.e.: <http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3.x/> Since Tomcat 3.3.x is in maintenance mode and very close to final release, the statement on the Binary and Source pages about Nightly builds being "unstable (a.k.a. dynamite!)" doesn't apply to Tomcat 3.3.x. Cheers, Larry > -----Original Message----- > From: Neo Gigs [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 13, 2002 9:34 PM > To: Tomcat Users List > Subject: Re: Tomcat shutdown > > > thanks alot Larry, i cook my problem b4 read ur email by > restarting the Solaris box. Another thing is i dun c any > Tomcat 3.3.1 at Jakarta-Tomcat website. Another issue is i > was trying to untar the tomcat 4.x but yet my Sun box does > not have GNOME compatible Tar, so i was unable to use the > latest version of Tomcat....what a annoying stuff... > > ----- Original Message ----- > From: "Larry Isaacs" <[EMAIL PROTECTED]> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > Sent: Wednesday, March 13, 2002 9:24 PM > Subject: RE: Tomcat shutdown > > > > The conf/ajp12.id file is written by the Ajp12Connector in your > > server.xml. It stores the port, host, and optional password to be > > used for shutdown. The shutdown process tries to read this file to > > get this information to you don't have to supply it on the command > > line. Thus, you can change the connector port in server.xml and > > shutdown will use the new port automatically. > > > > There isn't much detail about your situation to work with, > so I will > > guess you are using *nix. There was a bug/feature in the tomcat.sh > > file for Tomcat 3.3(a) where it could optionally wait for the > > existence of the ajp12.id file. Thus, the script would not > exit until > > Tomcat startup was well under way. This could help with automated > > testing. For this to work, the tomcat.sh script would > delete any old > > ajp12.id file. This had the unfortunate side effect of > deleting the > > ajp12.id file if you started Tomcat twice. The second one > deletes the > > file and then fails to create a new one because Tomcat > doesn't start a > > second time since the ports are in use. Because of this, > deletion of > > the ajp12.id file has been removed from the tomcat.sh script for > > Tomcat 3.3.1. I don't have another explanation as to why the file > > might be missing. > > > > Reguardless of why the ajp12.id file is missing, you can > specify all > > needed information on the shutdown command line. Assuming > the default > > server.xml file, the following command should be sufficient > (assumes > > the current directory is TOMCAT_HOME): > > > > bin/shutdown.sh port=8007 > > > > or > > > > bin\shutdown.bat port=8007 > > > > Cheers, > > Larry > > > > > > > -----Original Message----- > > > From: Neo Gigs [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, March 13, 2002 1:29 AM > > > To: Tomcat Users List > > > Subject: Tomcat shutdown > > > > > > > > > Hi there, > > > > > > I had a problem in shutdown tomcat when it says cannot locate > > > ajp12.id in TOMCAT_HOME\conf directory. Is there any > possible way to > > > shutdown? > > > > > > Neo > > > > > > > -- > > To unsubscribe: > <mailto:tomcat-user-> [EMAIL PROTECTED]> > > For > additional commands: > <mailto:[EMAIL PROTECTED]> > > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
