I can answer some of these...
1) have a look at your Tab Identifier in Application-Wide preferences... you might
find that by changing that you can make the log events split across tabs that are even
more useful to you than your original setup.
2) enable your webstart console (assuming you're using webstart chainsaw) and check
the log. Look for exceptions. You might have an OutOfMemory (so make the log file
smaller - I now use a RollingFileAppender with a 50MB limit for creating chainsaw log
files) or you might have a half-finished log4j event - check at the beginning and end
of the file you're trying to load to see if any of the events were truncated. Also
you should NOT include the <?xml version=1.0> etc in the file you're trying to load...
ONLY the events produced by your XMLLayout appender.
1) there is no mechanism... the most commonly recommended solution seems to be to add
an AsynchAppender. I've had some success using a JMSAppender, with a JMS Topic local
to the application's (in my case weblogic) app server, and then connect chainsaw to
the topic using a JMSReceiver. This approach isn't completely straightforward, however
- the biggest hurdle being that weblogic doesn't work well under webstart!
2) the chainsaw client seems to be able to handle a big load admirably!
Hope that helps.
Cheers,
Stephen
"Shai Simchi"
<[EMAIL PROTECTED] To: <[EMAIL PROTECTED]>
ke.com> cc:
Subject: Chainsaw v2 tab names and a
few more general questions
29/07/2004 08:47
Please respond to
"Log4J Users
List"
Hi !
I have been using chainsaw for some time now and have encountered 2 problems lately:
1) I am using a socket receiver to receive log messages from a few servers. so far I
had all the log messages showing up in the same tab that
was names by the name I gave the receiver. for some reason now it is split for a
few tabs - each server sending log messages to that socket
has a tab of its own. is there a way to solve that problem ?
2) I am trying to open an XML file but after the loading progress bar is done I get
nothing so I cant view the log messages within that file.
In addition I would like to ask a few little questions if possible:
1) using the socket receiver - assuming the server has a very big load of messages to
send to the socket - how is it dealing with the load ?
is it using a queue ? what is the mechanism on the distributing side to deal with
that load ?
2) on the client side ? is the socket listening only or polling the server ? how does
the client deal with a very big load ?
In general i'm asking about possible bottlenecks under heavy load and the possibility
of creating a load on out application servers.
thanks a lot,
Shai Simchi
Invoke Solutions Ltd.
+972-3-5756828 (ext. 206)
+972-66-227746 (mobile)
+972-3-5756829 (Fax)
mailto:[EMAIL PROTECTED]
www.invoke.com
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
