lumberjack-devel

[Lumberjack-devel] ADV: Reciprocal Links Service * Increase Your Website's Link Popularity

[cindy <ci...@st...>]

To remove your email address click the link below:
http://www.StarLinker.com/remove.asp?2043hg2w098y2
-------------------------------------------------------------------------------------------

The best way to drive traffic to your website is by using www.StarLinker.com.

They offer a FREE links page management solution which will also increase your link popularity.

Sign up for FREE.

3 Simple Set Up Steps

1. Set up your link account.
2. Select link partners.
3. Put your linking code on your links page.
You're Done!

Sign Up FREE Now at http://www.StarLinker.com?6


***

[Lumberjack-devel] Re: Clarification (was pl. help)

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

Matt,

Now I know the source of all confusion.  Its me, but not my programming!
Looks like there is another Lumberjack, the logging API implementation on
sourceforge.net.  The first time I downloaded the stuff, I forgot to bookmark
and the next time I searched for it for mailing my problem, I found the other
one.  I found a different name under developer and was surprised, but thought
it was a change.  Now I searched Sourceforge again and found the other
Lumberjack too.

Sorry for the confusion,
Balla


Matt Luker wrote:

> ko...@re... wrote:
> > I'm going to go out on a limb here, but if you put your test class in
> > the package java.util.logging it will send that request to the
> > bootloader--which is native.  It would be my guess that the exception
> > you are encountering is the bootloader becoming very confused or dying
> > because it thinks it has a critical error or security breach.
> >
> > Using the lumberjack-0.8.1 package and JDK 1.2.2, I was able to get it
> > running and working using the instructions in the READMEs.
> >
> > The classes are under com.redstarhackers.lumberjack.*.
>
> I stated what I think the problem is, but not the solution ... oops!
>
> I would move your class from java.util.logging to balla or some default
> package.  The java.* packages are reserved and I would be unsure how
> putting a class in that tree would behave on all platforms.
>
> Instead of java.util.logging, call it balla.logging or com.techone.logging.
>
> Let me know if that helps.
>
> Matt

[Lumberjack-devel] Clarification (was pl. help)

[<ko...@re...>]

ko...@re... wrote:
> I'm going to go out on a limb here, but if you put your test class in
> the package java.util.logging it will send that request to the
> bootloader--which is native.  It would be my guess that the exception 
> you are encountering is the bootloader becoming very confused or dying 
> because it thinks it has a critical error or security breach.
> 
> Using the lumberjack-0.8.1 package and JDK 1.2.2, I was able to get it
> running and working using the instructions in the READMEs.
> 
> The classes are under com.redstarhackers.lumberjack.*.

I stated what I think the problem is, but not the solution ... oops!

I would move your class from java.util.logging to balla or some default
package.  The java.* packages are reserved and I would be unsure how 
putting a class in that tree would behave on all platforms.

Instead of java.util.logging, call it balla.logging or com.techone.logging.

Let me know if that helps.

Matt

Re: [Lumberjack-devel] pl. help

[<ko...@re...>]

Balla,

ba...@te... wrote:
> That is all the code that I have, and I guess it is sufficient for a simple
> test.  As for the java.util.logging package if I am not mistaken it is part of
> the distribution of lumberjack, i.e., it comes with their logging.jar file.

Just to make sure I wasn't crazy, I downloaded 0.8.1 and checked the 
tar ball to make sure.  There is no package called java.util.logging.

>  I am totally confused now.  Isn't that the right way to do?

Me too, but I think we might have your problem ...

I'm going to go out on a limb here, but if you put your test class in
the package java.util.logging it will send that request to the
bootloader--which is native.  It would be my guess that the exception you are encountering is the bootloader becoming very confused or dying because
it thinks it has a critical error or security breach.

Using the lumberjack-0.8.1 package and JDK 1.2.2, I was able to get it
running and working using the instructions in the READMEs.

The classes are under com.redstarhackers.lumberjack.*.

I did have some problems with getting it to build under NT and Cygwin.
Apparently the Cygwin people changed how it works, so it no longer 
builds the same.  I'll try and fix that and update the docs.

The docs contain information on how to run a test client setup.
If you want to try your own client, take a look at how 
com.redstarhackers.lumberjack.CLIMonitor is put together.
If you want to try and use it in an application, take a look at
EventGenerator for how to embed the source object and how to use it.

Don't forget to change your java policy file to allow you to create
sockets.

Let me know if you need any more help.  I have another release I have
been working on.  I can try and put that up if you would like to use it.
It adds some convenience classes for the test cases, etc.  It has a few
changes in the code base, but most of the work has been on trying to finish
the DB monitor classes.

I'll also crank up my NT instance and install the latest cygwin and see
if I can't fix the build problems.

Matt

Re: [Lumberjack-devel] pl. help

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

Matt,

That is all the code that I have, and I guess it is sufficient for a simple
test.  As for the java.util.logging package if I am not mistaken it is part of
the distribution of lumberjack, i.e., it comes with their logging.jar file.  I
am totally confused now.  Isn't that the right way to do?

So, the Java class that I use, the compilation and execution batch files, are
all complete and I do not use anything apart from that in my test code.

Thanks,
Balla




Matt Luker wrote:

> Balla,
>
> I've loaded up my NT JDK-1.3 system, and I'm a bit confused.  You have an
> import for java.util.logging.* and you are having problems with
> java.util.logging.ConsoleHandler.  That package does not appear to be a
> part of my JDK (same build for NT).  Where are you getting that package?

>
> As a side note, I have tested this under IBM's JDK-1.3 on Linux and it
> works fine--not that it rules out an NT problem, but I believe there is
> nothing fundementally wrong with the lumberjack-0.8.1 package that would
> cause a JNI exception under 1.3 NT.
>
> Please send me the entire java source file for your test program so I
> can take a look at it.  Also let me know where you are getting this
> java.util.logging package--I can't find it in the JDK or in the JDK docs.
>
> Thanks,
> Matt
>
> ba...@te... 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
> >
> >
> >
> >
> > _______________________________________________
> > Lumberjack-devel mailing list
> > Lum...@li...
> > http://lists.sourceforge.net/lists/listinfo/lumberjack-devel
> >

Re: [Lumberjack-devel] pl. help

[<ko...@re...>]

Balla,

I've loaded up my NT JDK-1.3 system, and I'm a bit confused.  You have an
import for java.util.logging.* and you are having problems with
java.util.logging.ConsoleHandler.  That package does not appear to be a
part of my JDK (same build for NT).  Where are you getting that package?

As a side note, I have tested this under IBM's JDK-1.3 on Linux and it 
works fine--not that it rules out an NT problem, but I believe there is
nothing fundementally wrong with the lumberjack-0.8.1 package that would
cause a JNI exception under 1.3 NT.

Please send me the entire java source file for your test program so I
can take a look at it.  Also let me know where you are getting this
java.util.logging package--I can't find it in the JDK or in the JDK docs.

Thanks,
Matt

ba...@te... 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
> 
> 
> 
> 
> _______________________________________________
> Lumberjack-devel mailing list
> Lum...@li...
> http://lists.sourceforge.net/lists/listinfo/lumberjack-devel
> 

[Lumberjack-devel] 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