Re: Remote Logging using Log4J -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Remote Logging using Log4J
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 09 Mar 2006 15:50:15 -0600
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

cornelius, chad wrote:
> All I would like to do is log to a file on the IFS using a log listener.
> We have a server that is not internal, so accessing the logs from that
> server is difficult.  It doesn't have to log to the ISeries either.  It
> could log to another windows server within our network if need be.

I've used the SocketAppender to log to chainsaw (log4j gui log viewer),
which wasn't hard at all, but never written a log listener.

Check out the source for chainsaw for examples.

david

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.