facebook

Too many debug messages with Tomcat 5

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #243236 Reply

    Hi,

    I have written a java web app deployed on Tomcat 5. When I startup Tomcat from MyEclipse, the server takes a long time to come up because it spits out alot of DEBUG level log messages about various tag elements it is validating. Examples of the message are like this:

    
    DEBUG [2005-12-16 13:42:09,759] {main} -   New match='web-app/mime-mapping'
     DEBUG [2005-12-16 13:42:09,759] {main} -   Fire begin() for CallMethodRule[methodName=addMimeMapping, paramCount=2, paramTypes={java.lang.String, java.lang.String}]
     DEBUG [2005-12-16 13:42:09,759] {main} - Pushing params
     DEBUG [2005-12-16 13:42:09,759] {main} - characters(
            )
     DEBUG [2005-12-16 13:42:09,759] {main} - startElement(,,extension)
     DEBUG [2005-12-16 13:42:09,759] {main} -   Pushing body text '
            '
     DEBUG [2005-12-16 13:42:09,759] {main} -   New match='web-app/mime-mapping/extension'
     DEBUG [2005-12-16 13:42:09,759] {main} -   Fire begin() for CallParamRule[paramIndex=0, attributeName=null, from stack=false]
     DEBUG [2005-12-16 13:42:09,759] {main} - characters(zip)
     DEBUG [2005-12-16 13:42:09,759] {main} - endElement(,,extension)
     DEBUG [2005-12-16 13:42:09,759] {main} -   match='web-app/mime-mapping/extension'
     DEBUG [2005-12-16 13:42:09,759] {main} -   bodyText='zip'
     DEBUG [2005-12-16 13:42:09,759] {main} -   Fire body() for CallParamRule[paramIndex=0, attributeName=null, from stack=false]
     DEBUG [2005-12-16 13:42:09,759] {main} -   Popping body text '
            '
     DEBUG [2005-12-16 13:42:09,759] {main} -   Fire end() for CallParamRule[paramIndex=0, attributeName=null, from stack=false]
     DEBUG [2005-12-16 13:42:09,759] {main} - characters(
            )
     DEBUG [2005-12-16 13:42:09,759] {main} - startElement(,,mime-type)
     DEBUG [2005-12-16 13:42:09,759] {main} -   Pushing body text '
            
            '
     DEBUG [2005-12-16 13:42:09,759] {main} -   New match='web-app/mime-mapping/mime-type'
     DEBUG [2005-12-16 13:42:09,759] {main} -   Fire begin() for CallParamRule[paramIndex=1, attributeName=null, from stack=false]
     DEBUG [2005-12-16 13:42:09,799] {main} - characters(application/zip)
     DEBUG [2005-12-16 13:42:09,799] {main} - endElement(,,mime-type)
     DEBUG [2005-12-16 13:42:09,799] {main} -   match='web-app/mime-mapping/mime-type'
     DEBUG [2005-12-16 13:42:09,799] {main} -   bodyText='application/zip'
     DEBUG [2005-12-16 13:42:09,799] {main} -   Fire body() for CallParamRule[paramIndex=1, attributeName=null, from stack=false]
     DEBUG [2005-12-16 13:42:09,799] {main} -   Popping body text '
    

    This is annoying everytime I have to start up the server and it takes the server something like 3-4 mins to startup. In my server.xml I’ve put every instance of the debug attribute to 0. And my web.xml does not specify any debug levels. Can someone help me turn these offs. Also, I have added JSF, Spring and Hibernate capabilities to this project.

    Below is my system summary:
    *** Date: Fri Dec 16 13:42:37 PST 2005

    *** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.4.2_08

    *** MyEclipse details:
    MyEclipse Enterprise Workbench

    Version: 4.0.3 GA
    Build id: 20051025-4.0.3-GA

    *** Eclipse details:
    Eclipse SDK

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Platform

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse RCP

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Java Development Tools

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Plug-in Development Environment

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse Project SDK

    Version: 3.1.1
    Build id: M20050929-0840

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -launcher
    C:\javadev\eclipse_3.1.1\eclipse.exe
    -name
    Eclipse
    -showsplash
    600
    -exitdata
    c80_58
    -vm
    C:\javadev\j2se\j2sdk1.4.2_08\bin\javaw.exe

    #243250 Reply

    Scott Anderson
    Participant

    That’s the first time I’ve seen messages like that so it’s definately not a default Tomcat setting. I typically just download and unzip a copy and use it without modification and this doesn’t occur. Can you try doing that and then seeing if the messages still occur with your web app? Somehow, it looks like Tomcat itself is in debug mode and I neither know how to turn that on or off.

    #243257 Reply

    Greg
    Member

    I have seen these same type messages if I was using an incorrect version of JSTL. Are you using or deploying JSTL libraries?

Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: Too many debug messages with Tomcat 5

You must be logged in to post in the forum log in