I wouldn't say "mis-configured". When I changed from a similar configuration to a logger for all the jk stuff (e.g. log4j.category.org.apache.jk=WARN,filer), the request dumps went away. I think the issue was that the commons logging wrapper for a non-existent logger had a level of 0, which registered as "trace enabled", which meant some classes in the jk package dumped the whole request. For me, it was file uploads, so catalina.out was very large indeed. I also had a clue in that the catalina.out entry was prefixed by some debugging information from the jk classes. Is there anything preceding the dump of the request body in your logs? Like "Data: ..."?
Benjamin J. Armintor Operations Systems Specialist ITS-Systems: Mainframe Group University of Texas - Austin tele: (512) 232-6562 email: [EMAIL PROTECTED] -----Original Message----- From: Mike Curwen [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 24, 2004 7:18 PM To: 'Tomcat Users List' Subject: RE: Request parameters in catalina.out Just a "me too". Slackware 9.1 Apache 2 (sorry, can't find minor version) Tomcat 4.1.30 JK 1.2 I get the same sort of thing in my catalina.out, and only on POST submissions. If I switch my form temporarily to GET, the dump goes away. Here's my server.xml (which has been trimed from the 'out of the box' one): <Server port="11005" shutdown="SHUTDOWN" debug="0"> <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" debug="0"/> <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" debug="0"/> <!-- Define the Tomcat Stand-Alone Service --> <Service name="Tomcat-Standalone"> <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8080" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000" useURIValidationHack="false" disableUploadTimeout="true" /> <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 11009 --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="11009" minProcessors="5" maxProcessors="150" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" useURIValidationHack="false" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" /> <!-- Define the top level container in our container hierarchy --> <Engine name="Standalone" defaultHost="localhost" debug="0"> <!-- Global logger unless overridden at lower levels --> <Logger className="org.apache.catalina.logger.FileLogger" prefix="hosts_log." suffix=".txt" timestamp="true"/> <Realm className="org.apache.catalina.realm.UserDatabaseRealm" debug="0" resourceName="UserDatabase"/> <!-- Define the default virtual host --> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true"> <Logger className="org.apache.catalina.logger.FileLogger" directory="logs" prefix="localhost_log." suffix=".txt" timestamp="true" /> <Context path="" docBase="ROOT" debug="0" /> </Host> <Host name="devstar.globallyboundless.com" debug="0"> <Context path="" docBase="/home/data3/me20/" defaultSessionTimeOut="60" reloadable="true" > <Resource name="mail/Session" auth="Container" type="javax.mail.Session"/> <ResourceParams name="mail/Session"> <parameter> <name>mail.smtp.host</name> <value>mail.globallyboundless.com</value> </parameter> </ResourceParams> </Context> </Host> </Engine> </Service> </Server> Where's my dumper? As for log4j, I've got a log4j file at $CATALINA_HOME/common/classes that contains: log4j.category.org.apache.jk.common.ChannelSocket=WARN, filer log4j.additivity.org.apache.jk.common.ChannelSocket=false log4j.category.org.apache.jk.server.JkCoyoteHandler=WARN, filer log4j.additivity.org.apache.jk.server.JkCoyoteHandler=false log4j.appender.filer=org.apache.log4j.RollingFileAppender log4j.appender.filer.layout=org.apache.log4j.PatternLayout log4j.appender.filer.layout.ConversionPattern=%-5p %c - [%m] %d{ISO8601}%n log4j.appender.filer.File=/usr/local/applications/tomcat-4.1.30-1/logs/d ebug .catalina log4j.appender.filer.MaxFileSize=100KB log4j.appender.filer.MaxBackupIndex=4 This was an attempt (so far successful) to shut off messages like: [Thread-14] INFO common.ChannelSocket - connection timeout reached and [Thread-121] INFO server.JkCoyoteHandler - RESET Is it mis-configured? Thanks, MC --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
