I'll bet they *do* get created. You just don't know where to look. What does your config look like? Does it use relative paths to the files? Keep in mind, relative paths are relative to the directory from which the JVM started. So, if you start on the command line, the path in the config file is relative to the current directory in the command shell.
OTOH, When you start up using a service, unless you define the startup directory, it will default to "C:\WINDOWS\system32" (or the equivalent on your windows box). Furthermore, if your path includes a directory name, such as "./logs/mylog.log", and said directory doesn't exist already under "C:\WINDOWS\system32", then Log4j won't bother creating it for you. You have to make sure it exists before Log4j can write to the location. Look into that and let us know what you find. Jake Quoting Mirza Abbas Raza <[EMAIL PROTECTED]>: > All, > > The log4j framework doesn't seem to write to the logs when weblogic is run as > windows service. As I understand, the two things needed for the log4j > framework are: > - log4j.jar in classpath > - log4j.properties as -Dlog4j.configuration. It contains the necessary > configuration for logging. > > Both of the above mentioned artifacts are found correctly configured in the > utilities that were used to create the windows service. I have used both bea > provided utility and Java Service Wrapper from Tanuki Software. When weblogic > is started after the service installation, log files that were supposed to be > created by log4j don't appear. The ironic part is that when weblogic is > started manually, the log files do appear. Is there a known workaround for > this scenario? I appreciate any help. > > Environment info: > OS - Windows 2000 server > JDK - 1.4.2 > Weblogic - 8.1 > log4j - 1.2.7 > > Thanks, > Abbas > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
