Hi there,
What I always do is install a generic service initializing a socket server. This service is initialized using a properties file or an XML file.
In the classpath of the application server is a file log4j.poroperties containing only the following lines:
# BEGIN
# Attach appender SOCKET to root. Set root priority to Prority.DEBUG.
log4j.rootCategory=DEBUG, SOCKET
log4j.appender.SOCKET=org.apache.log4j.net.SocketAppender
log4j.appender.SOCKET.RemoteHost=localhost
log4j.appender.SOCKET.Port=<port>
# END
This way, all messages are send to the socket appender and the generic server is writing them down according its configuration.
Gino.
"""
(o -)
--o00-U-00o---------------------
In a world without fences...
Who needs gates?
--------------------------------
-----Original Message-----
From: Young, Jim [mailto:[EMAIL PROTECTED]]
Sent: woensdag 22 augustus 2001 21:21
To: Log4j-User (E-mail)
Subject: Log4J & WebSphere
Hi,
I am trying to move an application from VisualAge Java and Tomcat to
WebSphere 3.5.4 but I can not get log4j to work. Within the Tomcat
environment I can initialize log4j simply by placing my log4J.properties
file in the WEB-INF/classes directory or creating a Servlet to initialize
log4j. Both ways work fine with Tomcat but not with WebSphere.
1) Can I simply put the log4j.properties file in some folder in WebSphere?
2) Can I initialize it using a Servlet?
Any help would be appreciated,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
