You can download the chainsaw bundle for your platform and modify the .bat
file to change the -Xms and -Xmx settings to give the VM more memory.
Re: application-wide cyclic buffer value
Cyclic buffering is a per-tab setting and is enabled by default.
Setting the cyclic buffer to X means for each
Hi all,
I am using Chainsaw V2 to manage log messages coming from a C++ application,
currently the amount of messages that Chainsaw is receiving is very huge and
so we are getting "Out of Memory" errors...
Is there any way to increase the Java Heap Space when launching Chainsaw? I
have seen somew
Scott, now is working fine, thanks a lot for your quick responses!
regards,
Mh
2009/3/26 Scott Deboy
> You have to add the appender to your root logger..
>
>
>
>
>
>
> Scott
>
> On Thu, Mar 26, 2009 at 10:51 AM, Moley Harey
> wrote:
>
> > Hi againScott, sorry to disturb you with
You have to add the appender to your root logger..
Scott
On Thu, Mar 26, 2009 at 10:51 AM, Moley Harey wrote:
> Hi againScott, sorry to disturb you with this...
>
> I have added the appender in my Log4j config file and now it looks like:
>
>
> "log4j.dtd">
> http://jakarta.
Hi againScott, sorry to disturb you with this...
I have added the appender in my Log4j config file and now it looks like:
http://jakarta.apache.org/log4j/";
debug="false">
When I start
Correct - you can add appender definitions to the same Chainsaw
configuration file that contains the receiver definition, and the appenders
will process the events received by Chainsaw.
Scott
On Thu, Mar 26, 2009 at 10:18 AM, Moley Harey wrote:
> Hi Scott,
>
> 2009/3/26 Scott Deboy
>
> > You c
Hi Scott,
2009/3/26 Scott Deboy
> You can include in Chainsaw's configuration any appenders you'd like, which
> will cause any events received by the receivers to be propagated to the
> appenders automatically.
How can I do that?
What I am doing now is to launch Chainsaw and when I am prompted
You can include in Chainsaw's configuration any appenders you'd like, which
will cause any events received by the receivers to be propagated to the
appenders automatically.
You can also save logging events as XML in Chainsaw via the file menu (note,
whatever events are displayed are saved, so you
Hi again,
I have done the following test and is working fine:
1. Update my log4cxx.properties file to send all messages through a
XmlSocketAppender like this:
log4j.appender.A1=org.apache.log4j.net.XmlSocketAppender
log4j.appender.A1.Port=4560
log4j.appender.A1.RemoteHost=127.0.0.1
2. Launch Ch
Hi Dmitry and old,
Do you know if the available SimpleSocketServer already include the
possibility of using it with a XMLSocketReceiver?
Or does log4j provide something similar to the code used in Chainsaw?
Thanks in advance,
Mh
2009/3/26 Dmitry
> On the server side you must use XML based rec
On the server side you must use XML based receiver as well.
Non java applications (c,c++,.net,etc..) must send logging events in XML
serialized form and get reconstructed on the server into Java objects
from this XML.
--
Kind regards,
Dmitry
www.moonlit-software.com
Moley Harey wrote:
Hi, th
Hi, thanks for your answers...
I changed the appender in my log4cxx properties file to be a
XMLSocketAppender and now I get the following exception when trying to
connect to my SocketServer:
2009-03-26 09:35:08,528 INFO NRTSocketServer - NRTSocketServer :: Connected
to client at /127.0.0.1
2009-
On Mar 25, 2009, at 12:29 PM, Scott Deboy wrote:
I'm not sure what format log4cxx's SocketAppender uses to send logging
events.
Try using an XMLSocketAppender on the log4cxx side and an
XMLSocketReceiver
on the SimpleSocketServer side.
log4cxx 0.9.7 (a pre-ASF release) used a platform dep
You must use XMLSocketAppender to send log from any non-Java client to
Java server.
Put something like this into your C++ properties file :
log4j.appender.A1=org.apache.log4j.net.XMLSocketAppender
log4j.appender.A1.RemoteHost=localhost
log4j.appender.A1.Port=12345
It should work..
Kind regards,
I'm not sure what format log4cxx's SocketAppender uses to send logging
events.
Try using an XMLSocketAppender on the log4cxx side and an XMLSocketReceiver
on the SimpleSocketServer side.
Scott
On Wed, Mar 25, 2009 at 10:17 AM, Moley Harey wrote:
> Hi folks,
>
> I have implemented a Java Simple
Hi folks,
I have implemented a Java SimpleSocketServer application that is running
with log4j version 1.2, I have done a test Java class that initialize the
logging and sends a couple of messages to the SimpleSocketServer and works
fine, all messages sent by the test class are succesfully written
16 matches
Mail list logo
