Sudhakar,
The javadoc for org.apache.log4j.net.SocketServer clearly states that you
may have a configuration file for each client that connects to it, and if
not present a generic configuration file is applied.
Hope this helps,
--
Thomas
| -Original Message-
| From: Satrasala, Sudhakar
: Monday, September 30, 2002 5:40 PM
To: 'Log4J Users List'
Subject: RE: SocketAppender help required
This is generally caused by either compiling your source using the "no debug
info" option or are using a JIT-compiler.
If the first, then just omit the "-g:none" opt
This is generally caused by either compiling your source using the "no debug
info" option or are using a JIT-compiler.
If the first, then just omit the "-g:none" option from the javac command.
If the second, I am not sure if there is anything you can do.
|-Original Message-
|Fr
- Original Message -
From: "Ceki Gülcü" <[EMAIL PROTECTED]>
To: "Log4J Users List" <[EMAIL PROTECTED]>
Sent: Saturday, July 13, 2002 6:09 PM
Subject: Re: SocketAppender ignoring ErrorHandler?
> At 13:19 13.07.2002 -0400, you wrote:
> >I've been p
At 13:19 13.07.2002 -0400, you wrote:
>I've been playing around with a simple configuration of a program sending
>its logging info
>to a central JVM and it appears that SocketAppender does what I want.
>
>However, if the central JVM is not running, the SocketAppender gives the
>following msg:
>
Scott,
> log4j.appender.SOCKET.locationInfo=true
>
> then the location info is only generated IF the socket
> appender initialized
> properly, not when the message is created?
Assuming that none of the layouts for any appenders the logging event will
be sent to print out the location informati
means
producing LocationInformation only for, say, ERROR and FATAL Level's - i
will look those up.
thanks!
-scott
-Original Message-
From: Mark Womack [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 04, 2002 4:02 PM
To: 'Log4J Users List'
Subject: RE: SocketAppender and LoggingEvent data
ion. I am hoping to get something equivalent
into an official future release.
-Mark
> -Original Message-
> From: Klein, Scott @ TW [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 04, 2002 10:10 AM
> To: 'Log4J Users List'
> Subject: RE: SocketAppender and LoggingE
so at the risk of looking like a complete idiot, here's the answer:
log4j.appender.SOCKET.locationInfo=true
doh!
missed the tree looking through the forest ;)
-Original Message-
From: Klein, Scott @ TW [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 03, 2002 3:18 PM
To: Log4J-User (E-mai
There is also the SimpleSocketServer class which might serve as a better
example than SocketNode itself.
-Mark
> -Original Message-
> From: Klein, Scott @ TW [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 7:51 AM
> To: 'Log4J Users List'
> Subject
o:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 9:19 PM
To: Log4J Users List
Subject: RE: SocketAppender (was: console/file config)
Hi Mark,
Can you please give me one example on how to use the SocketNode class
on the server side.
Thanks
Anand
> -Original Message-
> From: Mar
Hi Mark,
Can you please give me one example on how to use the SocketNode class
on the server side.
Thanks
Anand
> -Original Message-
> From: Mark Womack [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 29, 2002 10:56 PM
> To: 'Log4J Users List'
> Subject
Look at the SocketNode class. You can use this class on the receiving end
to read the logging events.
-Mark
> -Original Message-
> From: Sundararaman, Anand [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 29, 2002 7:18 AM
> To: Log4J Users List
> Subject: RE: console/file config
>
>
I use the following technique to view logged messages from different
machines:
1. Configure the webapp's SocketAppender to send messages to
'localhost';
2. Start up Chainsaw on my machine;
3. Use ssh to redirect the 4445 port on the webapp's machine to
mine. This is done with the command:
Hrrmm, maybe a JXTA appender...
-- Glen
- Original Message -
From: "Mark Derricutt" <[EMAIL PROTECTED]>
To: "Log4J Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 18, 2001 2:06 PM
Subject: SocketAppender
Hiya, I'm currently using the socket appender, and ChainSaw to remotely
w
ephen
-Original Message-
From: Carlos Costa Portela [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 20, 2001 10:09 AM
To: LOG4J Users Mailing List
Subject: Re: socketAppender
On Wed, 19 Sep 2001, Ishihara, Noriaki wrote:
> When I execute a command to start the SocketServer, it s
On Wed, 19 Sep 2001, Ishihara, Noriaki wrote:
> When I execute a command to start the SocketServer, it says port
> number 12345 (or any other port number) is not available. (or log4j
> server is not running.. something like that)
Can you send us the message? What operating system do you
Paul,
Thanks for your reply.
We have just started developing a simple "log4jSocketRelay", that uses log4j
for output.
As it is a relay, we want it to be as transparent as possible, and it does not
modify the log events, it just dispatches them, using log4j.
Questions:
- When was it useful to b
> >> Well, chainsaw already acts as a prety good socket listener.
> I know chainsaw, but we need more.
Well, chainsaw is open source - what about using it as a starting point and
expanding it to include what you want?
> >> But if I understand you correctly, you want the socket listener
> >> its
11:56
À : LOG4J Users Mailing List
Objet : Re: SocketAppender based filtering relay/router..
Well, chainsaw already acts as a prety good socket listener. But if I
understand you correctly, you want the socket listener itself to then re-log
messages to various sources? Why not just have this done in
Well, chainsaw already acts as a prety good socket listener. But if I
understand you correctly, you want the socket listener itself to then re-log
messages to various sources? Why not just have this done in the first place,
rather than going thorugh the overhead of relogging the same messages?
Any
Create a file named (ip address.lcf, i.e., 192.216.253.116.lcf. This is the
host that generated the log message and sent to SocketAppender) in a
directory on a machine where SocketServer is running. This file can contain
all the config info. IMHO, this is a good way as you can change the config
wi
At 08:17 12.04.2001 -0500, [EMAIL PROTECTED] wrote:
>1) The SocketAppender API explains "SocketAppenders do not use a layout.
>They ship a serialized
>LoggingEvent object to the server side." Does this mean I cannot configure
>the output format on the client side but I can on the server side.
Y
23 matches
Mail list logo
