logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Walter_Mar...@DellTeam.com>
Subject RE: Web Service Appender
Date Thu, 01 May 2014 14:26:33 GMT
Dell - Internal Use - Confidential
Not necessarily. Remember that the people who read these logs are not in the processing loop,
and therefore do not slow down the process,
What is required is an asynchronous thread or process to do the soap transfer during off cycles,
and storage to receive the messages from the
Processing stream. Some sort of queuing and thread, or database storage might be used.

-----Original Message-----
From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Sent: Wednesday, April 30, 2014 11:16 PM
To: Log4J Users List
Subject: Re: Web Service Appender

A web service to do what? Logging via SOAP would be extremely slow if every log event is a
single request. Can you elaborate on what you really want to do?


On Apr 30, 2014, at 9:10 PM, Evan J wrote:

> Thanks for verifying this. I thought I might be missing an obvious,
> and this has already been implemented by at least someone.
> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma wrote:
>> Evan, no I'm not aware of any appender that logs to a web service.
>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>> wrote:
>>> I searched around, but I could not find an off-the-shelf Appender
>>> that sends logs to a web service. Is there any?

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message