|
From: Leif M. <le...@ta...> - 2004-10-06 02:45:26
|
Alan,
From what you posted, I don't see a problem with how your
configuration. But it is not
possible to tell without seeing your full wrapper.conf file and the
debug output from the
startup of your application.
Add the wrapper.debug=true property and look closely at the full
java command that
the Wrapper generates and see if anything stands out. If you don't see
the problem, then
post that output back to this list and I'll take a look at it.
Cheers,
Leif
Alan Stewart wrote:
>
> I previously ran a command-line java app by specifying
>
> java -Dlog4j.configuration=log4j.daemon.properties -cp <class path
> entries> <main class> , which worked fine.
>
> I've now configured the app to run as a service and have specified
>
> wrapper.java.additional.1=-Dlog4j.configuration=D:/Java/zurich/log4j.daemon.properties
> in the wrapper.conf file, but log4j is not initializing correctly and
> I get the following the wrapper.log:
>
> INFO | jvm 1 | 2004/10/06 09:55:26 | Wrapper (Version 3.1.1)
> http://wrapper.tanukisoftware.org
> INFO | jvm 1 | 2004/10/06 09:55:26 |
> INFO | jvm 1 | 2004/10/06 09:55:26 | log4j:WARN No appenders
> could be found for logger (au.com.zurich.integration.MQMessageDaemon).
> INFO | jvm 1 | 2004/10/06 09:55:26 | log4j:WARN Please initialize
> the log4j system properly.
> STATUS | wrapper | 2004/10/06 09:55:28 | <-- Wrapper Stopped
>
> I've tried putting the full path to the log4.daemon.properties file in
> the configuration line above, but it till doesn't work.
>
> What am I doing wrong?
>
> Thanks
> Alan
|