1 2 Previous Next 17 Replies Latest reply on Jan 15, 2007 10:53 PM by None None Go to original post
      • 15. Re: Logging using java.util.logging.*?
        Tony Herstell Master

        I had no logging from seam at the debug level.

        It appeared when I logged at info level.

        To do things properly:
        You probably already know this but you have to fiddle with the JBoss config to get logging at Debug level... either change the default logger to debug or add a log4j logger that logs your packages at the debug level).

        This is probably not your bug; but may help another noobie.

        • 16. Re: Logging using java.util.logging.*?
          Tony Herstell Master

           

          "seamNoobie" wrote:
          I had no logging from seam at the debug level.

          It appeared when I logged at info level.

          To do things properly:
          You probably already know this but you have to fiddle with the JBoss config to get logging at Debug level... either change the default logger to debug or add a log4j logger that logs your packages at the debug level).

          This is probably not your bug; but may help another noobie.



          C:\Program Files\jboss-4.0.5.GA\server\default\conf\log4j.xml

          Hack the below to make it DEBUG apposed to INFO or add your own appender into the file...

           <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
           <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
           <param name="Target" value="System.out"/>
           <param name="Threshold" value="INFO"/>
          
           <layout class="org.apache.log4j.PatternLayout">
           <!-- The default pattern: Date Priority [Category] Message\n -->
           <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
           </layout>
           </appender>
          


          • 17. Re: Logging using java.util.logging.*?
            None None Master

            All of my log messages are at SEVERE level and none are showing up. When the EAR deploys, I don't even see that notice showing up on the console. It's like when there is a virt. host, ALL log info about that goes away.

            This is an absolute nightmare because I know my app is throwing an exception somewhere but I can't even figure out which class is throwing it.

            The most primitive form of debugging was probably some form of logging. Today, JBoss ships with:

            1. The built-in Java exception mechanism

            2. The built-in java.util.logging

            3. log4j

            4. Commons Logging perhaps?

            5. Seam Logger

            6. System.out

            and perhaps other components.... AND YET IT'S IMPOSSIBLE TO GET A LOG MESSAGE FROM AN APP WHEN THERE IS A VIRTUAL HOST!

            1 2 Previous Next