Re: [Wrapper-user] Log4j problem.

[Leif M. <le...@ta...>]

Doug,
    I 'm not a bit log4j user myself.  I had to read over the log to 
even see what
your problem is.  I assume it is the following two lines?

INFO   | jvm 1    | 2006/01/30 08:42:25 | log4j:WARN No appenders could 
be found for logger (bf.cbm.util.io.Loader).
INFO   | jvm 1    | 2006/01/30 08:42:25 | log4j:WARN Please initialize 
the log4j system properly.

    This is most likely because of a log4j configuration problem.  Ie 
the configuration
is invalid or more likely, the config file is not being found.   Log4j 
can locate its
configuration on the classpath or in your case by specifying a specific 
log file
using a system property.

    I assume that the -Dlog4j.configuration=log4j.xml syntax is 
correct.  This will be
looking for a file ./log4j.xml in the same directory as your 
wrapper.exe.   Is that where
it is located?  Remember that all relative paths are relative to the 
location of the
wrapper.exe.

Cheers,
Leif

Doug Tanner wrote:
>
> I have read the different threads dealing with Log4j problems, but 
> none of them seem to have posted the fix/conclusion to the problem.
>
>  
>
> Here is my wrapper.log file:
>
<snip log file>
>
>   
> Can anyone tell me if they see a problem with this setup?  I cannot 
> seem to get the wrapper to use the log4j.xml file so that I can 
> monitor the output of the java program that it is running.
>