RE: Web Service Appender

Dell - Internal Use - Confidential http://www.ibm.com/developerworks/library/ws-log4j/index.html -Original Message- From: Evan J [mailto:maps.this.addr...@gmail.com] Sent: Monday, May 05, 2014 8:29 AM To: Log4J Users List Subject: Re: Web Service Appender Hi Walter, Can you point me to w

RE: Web Service Appender

Dell - Internal Use - Confidential Marshalling and unmarshalling is indeed inefficient, being CPU intensive, which competes for cycles with the main processes. JMS appears to have internal queuing, persistence to disk, and Asynchronous transport acknowledgements. It would be good to relieve the C

RE: Web Service Appender

Dell - Internal Use - Confidential I just saying we have the ability to work with log4j directly at this point. That should be useful since a custom appender will probably be needed for speed reasons, There are appenders for web services already written and available as freeware Thanks Walter

RE: More maven build problems for log4j

Dell - Internal Use - Confidential No custom ~/.m2/settings.xml file that I know of Build results=> C:\Software\log4j2source\apache-log4j-2.0-rc1-src>mvn install [INFO] Scanning for projects... Downloading: https://repository.apache.org/content/repositories/r

RE: Web Service Appender

Dell - Internal Use - Confidential I take it we were discussing the possibilities for high speed production logging. Previous people have rightly pointed out that a simplistic approach using soap might be ineffecient -Original Message- From: Ralph Goers [mailto:ralph.go...@dslextreme.com

RE: Web Service Appender

Dell - Internal Use - Confidential What is needed is not only bundling which is a form of buffering, but also process overlap so that the transfers are held up to a point where the processing is more quiet And more cycles are available. Offloading to another processor using tux also accomplishes

RE: Web Service Appender

Dell - Internal Use - Confidential As I say there are a lot of architectural options. We need to decide on one. Having th ability to modify log4j should make whatever architecture is chosen cleaner. Thanks Walter -Original Message- From: Ralph Goers [mailto:ralph.go...@dslextreme.com]

RE: Web Service Appender

Dell - Internal Use - Confidential There are several architectural options . The cleanest might be to make a custom appender, and then do the queue removal and transport with a thread within Log4j itself. This has the advantage of not disturbing the current setup and interface for local logging

RE: Web Service Appender

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

RE: Web Service Appender

Dell - Internal Use - Confidential Try this url http://www.ibm.com/developerworks/library/ws-log4j/index.html -Original Message- From: Evan J [mailto:maps.this.addr...@gmail.com] Sent: Wednesday, April 30, 2014 7:21 PM To: log4j-user@logging.apache.org Subject: Web Service Appender I sea

More maven build problems for log4j

Dell - Internal Use - Confidential Could not build clean target for 1.2.17, could not build install target for 2.0. In each case maven libraries could not be found. Thanks wALTER

RE: maven build for source does not work

Dell - Internal Use - Confidential I would if I could, but I can't so I shan't... -Original Message- From: Remko Popma [mailto:remko.po...@gmail.com] Sent: Tuesday, April 29, 2014 8:32 AM To: Log4J Users List Subject: Re: maven build for source does not work Walter, It's open source thou

RE: maven build for source does not work

Dell - Internal Use - Confidential What? No maintenance on the latest released source? -Original Message- From: Scott Deboy [mailto:scott.de...@gmail.com] Sent: Monday, April 28, 2014 6:46 PM To: Log4J Users List Subject: Re: maven build for source does not work It is not true that we don

RE: maven build for source does not work

Dell - Internal Use - Confidential What no maintenance on the latest RELEASED source? -Original Message- From: Matt Sicker [mailto:boa...@gmail.com] Sent: Monday, April 28, 2014 6:01 PM To: Log4J Users List Subject: Re: maven build for source does not work We don't maintain 1.2.x anymore.

maven build for source does not work

Dell - Internal Use - Confidential 1) The pom file has to be updated to allow for maven-site-plugin 3.3 rather than 3.1 2) The mvm staging step gives a null pointer exception Apache.log4j-1.2.17 Thanks Walter