That is pretty much what we are trying. It was working up until installing this new component. Unfortunately, this new component uses what appears to be a custom logger wrapper which, no matter what we try, just does not utilize the existing current log4j init.
-----Original Message----- From: Sullivan, Sean C - MWT [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 5:04 PM To: 'Log4J Users List' Subject: RE: Config in app server envs Our situation: - Log4j 1.2.8 - two application servers in our cluster - five EAR's We use a single log4j.xml for all of our applications. log4j.xml is stored on the server's filesystem. We set JVM system property (log4j.configuration) so that Log4j can find our log4j.xml file -Sean > -----Original Message----- > From: Charles Hudak [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 1:01 PM > To: 'Log4J Users List' > Subject: RE: Config in app server envs > > There are obviously many ways to do this. > > The way I do it is I created a LogInitializer servlet that is loaded on > startup and uses a single configuration file. Since I'm really only > concerned about the logging from MY code and not any of the open > source/other components that I have installed, this works fine. > > The nice thing about this is I have written the servlet so that it can be > called in order to 'refresh' the logging properties if I need to change > them > on the fly. Since we have clustered servers, this servlet invokes the > refresh on each of the servers in the farm to re-initialized their logging > as well. > > Logging setup should NEVER be done by component writers (IMHO) unless the > component is standalone. Rather, they should provide logging in the code > that can be turned on and configured by the app deployer. If you have > groups > developing components that are under the same adminstrative control as you > (i.e. contractors or developers working for the same organization) then > everyone needs to get on the same page regarding logging. > > > -----Original Message----- > From: Ebersole, Steven [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 12:51 > To: Log4j user list (E-mail) > Subject: Config in app server envs > > > Whats the standard way to setup logging in an app server when some > components use a properties file for config and some use an xml file? > > Previously we had control of all deployed components on thats server, and > all the components used a file named log4j-config.xml located on the > various > classpaths. The only way I had found to acheive this was to set a > -Dlog4j.configuration=log4j-config.xml system property. That worked OK, > until now. Now there is a new component in the mix which attempts to use > a > properties file, but fails to iniitialize because of the > log4j.configuration > system property being set. > > How can I make this work, short of converting the third party properties > file into its XML representation. > > Also, is there a way (or plans for a way) to make a standard naming for > the > XML configs? Such that default init attempts to find log4j.properties, > and > then log4j.xml (or some other name)... > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
