In Windows:
If you have java 1.4, Java Web Start has it's own menu under start-programs.
file-preferences, advanced tab, check 'show java console'. You can also hit
the 'clear folder' button from there to remove Chainsaw from your web start
cache so it has to be downloaded again.
If you have
Scott Deboy wrote:
try enabling the webstart java console, in case this is triggering an uncaught
exception.
Sorry to appear thick, but could you tell me how to do this?
are you sure your app doesn't use mdc?
I don't think I know what mdc is. My app is a Tomcat webapp, mostly jsp'
try enabling the webstart java console, in case this is triggering an uncaught
exception.
are you sure your app doesn't use mdc?
you could also delete the user.dir/.chainsaw directory - shouldn't cause a
problem but that's where settings are stored.
-Original Message-
From: Bill Harre
At 10:51 AM 11/4/2005 -0800, you wrote:
>Is there any difference, advantage, etc. by doing
>
>Logger logger = Logger.getLogger(MyClass.class);
>
>versus doing
>
>Logger logger = Logger.getLogger(MyClass.class.getName());
>
>I've seen it both ways in documentation and examples and b
Thanks Scott,
I tried your suggestion and got some odd behavior. At first, it
created a tab in chainsaw, recorded one message, and stopped.
I tried repeatedly stopping and starting everything, and even taking
all other appenders out, but it never created the tab after that one
time.
I do no
On Fri, 04 Nov 2005 09:35:31 -0800, Mark Womack wrote:
> Do you have any actual timing or profiling information that would lead
> you to suspect that log4j is causing the problem, or just anecdotal
> experience? There is nothing I can think of that changed so much in any
> of the recent log4j rele
Change the order of appenders in your rootCategory entry, so that the
chainsaw appender is first in the list.
The reason: logging event changed between 1.2.x and 1.3 - events sent by
a 1.2.x socketappender can't contain location info (file, line, class,
etc) or MDC entries if you want them to be
The idea of using SocketHubAppender was very helpful, in theory for what
I want, but I'm having trouble getting it to work. Logging is working
fine to stdout and weblog, but chainsaw doesn't see anything. It
doesn't even create a tab for the receiver.
Here's my log4j config file:
log4j.root
Is there any difference, advantage, etc. by doing
Logger logger = Logger.getLogger(MyClass.class);
versus doing
Logger logger = Logger.getLogger(MyClass.class.getName());
I've seen it both ways in documentation and examples and both seem to
work the same way.
--
Do you have any actual timing or profiling information that would lead you
to suspect that log4j is causing the problem, or just anecdotal experience?
There is nothing I can think of that changed so much in any of the recent
log4j releases to account for the level of degradation you are describing
When the object starts call NDC.push and when the object ends call
NDC.pop. That should work.
On 11/4/05, Luca Ferrari <[EMAIL PROTECTED]> wrote:
> Hi,
> I'm pretty new to log4j and I'd like to solve a problem similar to the
> one of Nested Diagnostic Contexts, but without threads. Briefly, my
>
On Fri, 04 Nov 2005 00:55:22 -0500, Frank W. Zammetti wrote:
> One thing that I'm curious about... are you actually instantiating a new
> Logger on each class instantiation (in the constructor I would guess)?
> If so, you might want to try making it a static member so the Logger
> instantiation
Hi,
I'm pretty new to log4j and I'd like to solve a problem similar to the
one of Nested Diagnostic Contexts, but without threads. Briefly, my
problem is that I've got a few active objects executed by a few threads.
Once an active object has nothing to do, it releases the thread, that is
assig
13 matches
Mail list logo
