5 Replies Latest reply on Jan 4, 2002 5:54 PM by neut6o1

    Verbose JBoss Logging

    neut6o1

      I have a problem with JBoss 2.4.3 with tomcat 3.2.3. On startup, the amount jboss logs to the console when starting up the container and datasource and all the stuff it needs to begin is ridiculous. I am sure that it is slowing me down with all of the System.outs. I tried changing the threshold of the log4j in log4j.properties, but when I changed it from INFO to WARN, it now shows me only 4 lines, but does not let me know when it is finished starting up so that I can go to the website. Is there a way to log in between these extremes?

      Chris Heady

        • 1. Re: Verbose JBoss Logging

          Hi,

          Rather than changing the appender threshold,
          you can change the categories individually.

          log4j.category.org.jboss=WARN

          This will still show the started message
          because it doesn't go to an org.jboss category.

          You can control each category individually.
          To see the full category names
          change the conversion pattern to [%c] instead of
          [%c{1}] which only shows the last part.

          Regards,
          Adrian

          • 2. Re: Verbose JBoss Logging
            neut6o1

            Thanks warjort, for your help. It worked very well. I now have the exact amount of logging that I wanted. Even better than when I was on JBoss 2.2.2.

            I did try changing the conversion pattern to [%c] from [%c{1}]. However this did not change anything in the logging. I did it both on the default and console appender. Are you sure that shows the full category name?

            Chris Heady

            • 3. Re: Verbose JBoss Logging
              neut6o1

              One more thing, I see the entire category name in log4j logs that I have created, but not in ones like "[Container Factory]" and "[Default]". I guess those must be from a different log4j.properties file.

              Chris Heady

              • 4. Re: Verbose JBoss Logging

                Hi.

                JBoss used to use its own custom logger.
                It has gradually moved to log4j exclusively.
                As of 3.0 the old logger is gone.

                [Default] is System.out.println which log4j
                intercepts. :-)

                Regards,
                Adrian

                • 5. Re: Verbose JBoss Logging
                  neut6o1

                  Thanks again warjort. The information you have given me has really helped.