Hi Bill, Thanks for your answer and sorry for the delay in my reply!
I'm using standalong Tomcat 5.5 listening on port 80. I'm using jdk 1.5 on WinXP. I'm not using any special logging. I'm running Tomcat in a console, simply by typing "startup" in tomcat/bin. What I don't want happening is for the "Connection reset by peer: socket write error" to be displayed in the console window. Given this detailed information, would you mind refining your recommendation? Thank you very much in advance, Dola Chin --- Bill Barker <[EMAIL PROTECTED]> wrote: > > "Dola Woolfe" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Hi, > > > > I apologize for asking this question again for I > > remembering asking this question in the past, but > I > > can't find the response. > > > > What setting (and where) will suppress the > > aforementioned exception in the tomcat log? > > > > Including the Tomcat version helps ;-). > > I'm assuming that this is for the AJP/1.3 Connector. > The answer is to > change the logging level for that component to be > one higher than the level > in the message (in the latest version, it's at DEBUG > level and I don't > remember what it used to be). For example, if you > are using JDK1.4 logging > you would do something like: > org.apache.jk.common.level=SEVERE > > in your logging.properties file. > > > Thank you very much in advance, again! > > > > Dola > > > > > > > > __________________________________ > > Yahoo! Mail - PC Magazine Editors' Choice 2005 > > http://mail.yahoo.com > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
