Tomcat 5.5.27 Verbose Debug Messages

[tribina]

Hello,

I support a commercial application running under Tomcat 5.5.27. The application is BusinessObjects XIR2. This app comes bundled with Tomcat 5.0.27, but for security reasons I moved it to run under Tomcat 5.5.27.

The problem I have is that since I've moved it to run under the new version of Tomcat my stdout.log file is littered with DEBUG messages. I'm using the same WAR files that get deployed to the 5.0.27 instance.

sample stdout.log

173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - JspEngine --> /InfoView/main/main.jsp
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - ServletPath: /InfoView/main/main.do
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - PathInfo: null
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - RealPath: e:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\businessobjects#enterprise115#desktopl aunch\InfoView\main\main.jsp
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - RequestURI: /businessobjects/enterprise115/desktoplaunch/InfoView/main/main.do
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - QueryString: objId=0
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - Request Params:
173109 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - objId = 0
173516 [http-9080-3] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/businessobjects/enterprise115/desktoplaunch] - servletPath=/InfoView/main/headerPlus.jsp, pathInfo=null, queryString=null, name=null
173516 [http-9080-3] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/businessobjects/enterprise115/desktoplaunch] - Path Based Include
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - JspEngine --> /InfoView/main/headerPlus.jsp
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - ServletPath: /InfoView/main/headerPlus.do
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - PathInfo: null
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - RealPath: e:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\businessobjects#enterprise115#desktopl aunch\InfoView\main\headerPlus.jsp
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - RequestURI: /businessobjects/enterprise115/desktoplaunch/InfoView/main/headerPlus.do
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - QueryString: objId=0
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - Request Params:
173516 [http-9080-3] DEBUG org.apache.jasper.servlet.JspServlet - objId = 0


I have the standard logging.properties file that comes with Tomcat with the exception that I disabled the console handler.

I've googled how to disable this level of debugging, but have been unable to figure it out. According to some posts and the vendor, it was suggested I setup log4j. I did it following the instructions here. (http://tomcat.apache.org/tomcat-5.5-doc/logging.html)

With this it still yields the same output. The vendor then suggested I use the following log4j.properties

log4j.rootLogger=ERROR, stdout, TOMCAT

log4j.appender.stdout=org.apache.log4j.ConsoleAppe nder
log4j.appender.stdout.layout=org.apache.log4j.Patt ernLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ dd-MM-yy HH:mm:ss:SSS} - {%p} %c{2} Thread [%t]; %x %m%n

log4j.appender.TOMCAT=org.apache.log4j.DailyRollin gFileAppender
log4j.appender.TOMCAT.File=${catalina.home}/logs/tomcat.log
log4j.appender.TOMCAT.DatePattern='.'yyyy-MM-dd
log4j.appender.TOMCAT.layout=org.apache.log4j.Patt ernLayout
log4j.appender.TOMCAT.layout.ConversionPattern=%d{ dd-MM-yy HH:mm:ss:SSS} - {%p} %c{2} Thread [%t]; %x %m%n

However, this didn't help it either.

I've turned on -Dlog4j.debug to see what it does, but no where do I find where DEBUG level logging is getting turned on.

I've even added the following to the log4.properties at the recommendation of another post.

log4j.logger.org.apache.catalina.core=ERROR
log4j.logger.org.apache.catalina.session=ERROR
log4j.logger.org.apache.jasper.compiler=ERROR


Again, same result.

I don't have a clue where this level of debugging is getting set. Any help you guys can offer is greatly appreciated.

Thank you. -CB

[Kees de Kooter]

Default tomcat does not use log4j. That is why log4j properties have no effect.

Please take a look at the server.xml in the conf dir of your tomcat installation and check which logging related valves are enabled and how they are configured.

[kjkoster]

Dear tribina,

You could try to diff the configuration of the two tomcats you have (5.0.27 and 5.5.27) to see how they differ with respect to the logging configuration.

Also, there may be a log4j config file bundled in the WAR. Due to the way logging works in log4j and in Tomcat, Tomcat messages may be picked up and logged by the *application* log4j.

Kees Jan

[vthomer]

Default tomcat does not use log4j. That is why log4j properties have no effect.

Please take a look at the server.xml in the conf dir of your tomcat installation and check which logging related valves are enabled and how they are configured.

Hi,
I'm having this same issue...and printed/retyped the server.xml from one installation of 5.5.23 (not having the problem - at a different work site) here on my server.xml file at a new worksite. Unfortunately I spend a week between the two sites and am not allowed to xfer any information between the two.

Does anyone have any ideas where/how to fix this?
startup takes 20-30 seconds, any transactions are taking a long, long time too due to logging. i've compared context.xml and logging files

thanks,
Raj

[tribina]

Raj,

The solution I came up to this problem was to delete the log4j.properties from the desktoplaunch (i.e. Infoview) webapp. For some reason when this is booted it corrupts the logging verbosity.