javalogging-users — Email list for users of Lumberjack

[Lumberjack-users] Problem with Apache Commons Logging

[David O. J. <da...@da...>]

Hi,

I've run into a problem with Lumberjack and I'm hoping someone has a solve.  The
short of it is that Apache's Logging from the Commons Project doesn't work with
Lumberjack.  Basically, when Commons Logging uses their 'adapter' to publish
commons logging calls to the JDK 1.4 logging calls, Lumberjack appears to be
throwing exceptions or in some way not performing in a way that Commons expects
JSR47/JDK 1.4 logging to work.

The commons group 'resolved' it by changing the check so that lumberjack is
avoided, but I want lumberjack to be able to work with the JDK 1.4/JSR 47
support in Commons.

Has anyone else reported or seen a similar issue?  What is the resolution to
date on this?

--
David Orriss Jr.

[Lumberjack-users] [ANN] Lumberjack 0.9.2

[Brian G. <br...@gi...>]

Lumberjack 0.9.2 (the Java Logging API for JDKs 1.2 & 1.3) is out. This 
release adds an installer that will install Lumberjack into the proper 
place to use it. It requires that you have write permissions for the JRE 
directories, but if you have them it will bring up a simple GUI to 
install Lumberjack. The GUI checks to make  sure that Lumberjack is 
compatible (e.g. the JDK is 1.2.x or 1.3.x) and asks before overwriting 
any existing installation of the classes and logging.properties.

The RELEASE_NOTES describes the installer in more detail, as well as a 
couple of other options for using Lumberjack if you can't use the installer.

For the next release, the target is to get all the outstanding bugs 
fixed. Even though the holidays are coming up, I hope to have it out 
before the end of the year.

You can find Lumberjack at http://javalogging.sourceforge.net.

Thanks,
Brian Gilstrap

-- 
Brian R. Gilstrap
br...@gi...
Husband and father, Tai Chi practitioner, Software architect
Java developer, Macintosh User

"Doubtless, like all of us, he was many men, turned on one or another of 
his selves as occasion required, and kept his real self a frightened 
secret from the world."  --Will Durant

[Lumberjack-users] Lumberjack 0.9.1 is out

[Brian G. <br...@gi...>]

It brings Lumberjack in line with version 0.8 of the Java Logging APIs 
(JSR 47). There are a couple of outstanding bugs (see the sourceforge 
project page) but it should be quite usable.

Note that there were significant changes in the spec, such as how the 
hierarchy of loggers and their logging levels are handled. Before 
reporting a bug because something is different than in Lumberjack 0.8.7, 
please check the spec to make sure it isn't an official change in 
behavior :-).

Also, if you happened to download Lumberjack 0.9, please upgrade 
immediately to 0.9.1. I put out 0.9 before performing adequate testing 
and it has some pretty egregious bugs (sorry!).

Finally, I'll be creating a FAQ. And to get the ball rolling, here is 
one of the items that will appear (it's shown up several times recently):

Q: Why is it that my output doesn't always contain the proper names of 
the invoking class and method?

A: Unless you call logp or logrb and pass the class name and method name 
explicitly, there is no guarantee that your class and method names will 
be right. While Lumberjack and the 1.4 implementation try their best to 
determine the correct name of the class and method, it is not possible 
to be 100% correct, especially due to things like JIT/Hotspot 
optimizations. This is described in the 0.80 spec (see the last 
paragraph on page 11).

As always, feedback is appreciated.

Thanks,
Brian Gilstrap

[Lumberjack-users] parameters are ignored in SimpleFormatter

[Bruno H. <ha...@il...>]

Hello dear javalogging implementors,

Without this fix, an 'info' call with parameters ignores the
parameters, i.e. produces output like this:

Aug 17, 2001 04:00:15 PM ilog.cpl.util.IlpForwardingHandler publish INFO: >> event {0}

But what I need is output like this:

Aug 17, 2001 04:03:32 PM ilog.cpl.util.IlpForwardingHandler publish INFO: >> event ilog.cpl.network.NetworkModelEvent[ROOT_OBJECT_ADDED,model=ilog.cpl.network.IlpDefaultNetworkModel@114f6a,object=ilog.cpl.network.IlpDefaultNetworkNode@71dc3d]


Here is a fix.

diff -c -3 -r1.1.2.1 SimpleFormatter.java
*** SimpleFormatter.java	2001/08/17 13:25:49	1.1.2.1
--- SimpleFormatter.java	2001/08/17 14:07:22
***************
*** 51,57 ****
          msg.append( " " );
          msg.append( record.getLevel() );
          msg.append( ": " );
!         msg.append( record.getMessage() );
          msg.append( "\n" );
          return msg.toString();
      }
--- 51,57 ----
          msg.append( " " );
          msg.append( record.getLevel() );
          msg.append( ": " );
!         msg.append( formatMessage( record ));
          msg.append( "\n" );
          return msg.toString();
      }


And in order to avoid NullPointerExceptions coming from
Formatter.FormatMessage

Exception in thread "main" java.lang.NullPointerException
        at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:582)
        at java.util.ResourceBundle.getBundle(ResourceBundle.java:546)
        at java.util.logging.Formatter.formatMessage(Formatter.java:41)
        at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:55)
        at java.util.logging.StreamHandler.publish(StreamHandler.java:188)
        at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:55)
        at java.util.logging.LogManager.publish(LogManager.java:203)
        at java.util.logging.Logger.log(Logger.java:298)

I also commented out a piece of code in Formatter.FormatMessage:

diff -c -3 -r1.1.2.1 Formatter.java
*** Formatter.java	2001/08/17 13:25:47	1.1.2.1
--- Formatter.java	2001/08/17 14:07:22
***************
*** 34,39 ****
--- 34,40 ----
       * will not be available until JDK 1.4.
       */
      public String formatMessage( LogRecord record ) {
+ /*
          String key = record.getMessage();
          ResourceBundle bundle = record.getResourceBundle();
          if ( bundle == null ) {
***************
*** 49,54 ****
--- 50,57 ----
                  formatString = key;
              }
          }
+ */
+         String formatString = record.getMessage();
          Object[] parameters = record.getParameters();
          if ( parameters == null || parameters.length == 0 ) {
              return formatString;

All the best,

                  Bruno

[Javalogging-users] Re: pl. help

[Chandrasekhar B. <ba...@te...>]

Thanks Brian, version 0.8.3 helps!

"Brian R. Gilstrap" wrote:

> Chandrasekhar Balla wrote:
> >
> > > Hi,
> > >
> > > I am trying to use lumberjack with jdk1.3 (build 1.3.0-C) on NT
> > >
> > > and am getting this exception:
> > >
> > > # An EXCEPTION_STACK_OVERFLOW exception has been detected in native
> > code
> > > outside
> > >  the VM.
> > > # Program counter=0x5025c2c7
> > >
> > >
> > > It is a simple program that I tired out with the default
> > > logging.properties configuration.  The error seems to occur when the
> > > java.util.logging.ConsoleHandler is being loaded by the JVM.
> > >
> > > Thanks for any help,
> > > Balla
> > >
> > > The following is the code that I tried.
> > >
> > > ------------------------------------
> > >
> > > import java.util.logging.*;
> > >
> > > public class LogTest
> > > {
> > >  private static Logger logger = Logger.getLogger("LogTest");
> > >
> > >  public static void main(String[] args)
> > >  {
> > >   System.out.println("Testing Logging API");
> > >   // this is to test the Java logging facility
> > >   logger.info("a test message of level, INFO");
> > >   logger.fine("a test message of level, FINE");
> > >   logger.finer("a test message of level, FINER");
> > >   logger.finest("a test message of level, FINEST");
> > >  }
> > > }
> > >
> > >
> > > ----- compileit.bat
> > > echo off
> > >
> > > set
> > > CLASSPATH=%CLASSPATH%;D:\JavaLogging\Lumberjack-0.8.1\lib\logging.jar
> > >
> > > javac -g LogTest.java
> > >
> > >
> > > ----------- runit.bat
> > > echo off
> > >
> > > REM java -Xbootclasspath/a:C:\stuff\logging.jar <other args here>
> > >
> > > rem c:\jdk1.3\bin\java
> > > -Xbootclasspath/a:D:\JavaLogging\Lumberjack-0.8.1\lib\logging.jar
> > > LogTest
> > >
> > > c:\jdk1.3\bin\java -Xmx256 -verbose
> > > -Xbootclasspath/a:D:\JavaLogging\logging.jar LogTest
>
> Hi Balla,
>
> Thanks for trying out Lumberjack. I'm not sure why you are getting this
> error. However, I just put out a new release of Lumberjack (I've been
> working on more tests since the 0.8.1 release). Version 0.8.3 fixes a
> number of bugs, including one that could cause an infinite recursion.
> That would fit with you being out of stack space.
>
> Please download 0.8.3 and try again.
>
> ALSO, please do not put the logging.jar on your regular CLASSPATH. You
> should only need to put it on yoru bootclasspath (which you have done
> correctly above).
>
> Please let me know if you continue to have problems.
>
> Thanks,
> Brian
>
> --
> Brian R. Gilstrap
> br...@gi...
> Husband and father, Tai Chi practitioner, Software architect
> Java developer, Macintosh User
>
> "Doubtless, like all of us, he was many men, turned on one or another of
> his selves as occasion required, and kept his real self a frightened
> secret from the world."  --Will Durant

[Javalogging-users] pl. help

[Chandrasekhar B. <ba...@te...>]

Hi,

I am trying to use lumberjack with jdk1.3 (build 1.3.0-C) on NT

and am getting this exception:

# An EXCEPTION_STACK_OVERFLOW exception has been detected in native code
outside
 the VM.
# Program counter=0x5025c2c7


It is a simple program that I tired out with the default
logging.properties configuration.  The error seems to occur when the
java.util.logging.ConsoleHandler is being loaded by the JVM.

Thanks for any help,
Balla

The following is the code that I tried.

------------------------------------

import java.util.logging.*;

public class LogTest
{
 private static Logger logger = Logger.getLogger("LogTest");

 public static void main(String[] args)
 {
  System.out.println("Testing Logging API");
  // this is to test the Java logging facility
  logger.info("a test message of level, INFO");
  logger.fine("a test message of level, FINE");
  logger.finer("a test message of level, FINER");
  logger.finest("a test message of level, FINEST");
 }
}


----- compileit.bat
echo off

set
CLASSPATH=%CLASSPATH%;D:\JavaLogging\Lumberjack-0.8.1\lib\logging.jar

javac -g LogTest.java


----------- runit.bat
echo off

REM java -Xbootclasspath/a:C:\stuff\logging.jar <other args here>

rem c:\jdk1.3\bin\java
-Xbootclasspath/a:D:\JavaLogging\Lumberjack-0.8.1\lib\logging.jar
LogTest

c:\jdk1.3\bin\java -Xmx256 -verbose
-Xbootclasspath/a:D:\JavaLogging\logging.jar LogTest