The conf/ajp12.id file is written when Tomcat starts up. It stores at least the port number of the Ajp12Interceptor used to invoke the shutdown. It can also store a password and other info to help make shutting down more secure. When executing "tomcat.sh stop" or "shutdown.sh", Tomcat will try to read this file to determine the port and other info so it can send the shutdown request.
There is a known problem in that tomcat.sh deletes this file prior to starting. If you inadvertently start Tomcat twice, the second one deletes the file but doesn't get far enough to write a new ajp12.id. As a result, "shutdown.sh" won't find the file when you try to shut down the first instance. You can try creating a default one manually and enter "8007" (without the quotes) on the first line, followed by two blank lines. Then try shutting down again. Cheers, Larry > -----Original Message----- > From: Micheleen Harris [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 31, 2001 8:35 PM > To: [EMAIL PROTECTED] > Subject: Shutting down apache tomcat server > > > I am running the tomcat server version 3.3 on an Irix > machine. I am maintaining tomcat as well as writing > servlets therefore starting and shutting down the > server for developement purposes. Upon shutting down > the server recently I recieved the error: > > Can't read > /usr/tomcat/jakarta-tomcat-3.3//conf/ajp12.id > > 1. What does this mean? > 2. How do I fix it? > > Pleas help. Thank you. > > ~Micheleen > > __________________________________________________ > Do You Yahoo!? > Make a great connection at Yahoo! Personals. > http://personals.yahoo.com > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
