|
From: Leif M. <le...@ta...> - 2006-04-04 14:51:55
|
Karthikeyan,
As I understand Log4j, that all looks fine. You are specifying your
properties file using
a system property so it does not need to be on the classpath. I don't
usually use log4j
however. More a Apache Logkit fan.
What happens if you add this:
wrapper.java.classpath.7=D:/rmi-svc/properties
That will let logkit locate the file on the classpath. The system
property should be
working however.
Try setting the following property to see the full java command used
to launch the JVM:
wrapper.java.command.loglevel=INFO
Not too helpful. :-/ Anyone else with more log4j experience have
any ideas?
Cheers,
Leif
karthikeyan d wrote:
> Hi Leif,
>
> Thanks for your time and willingness to solve my issues. Please find
> attached the wrapper config file and my log4j.properties file.
>
> Appreciate your support very much in this regard.
>
>
> Thanks & Regards,
> D.karthikeyan.
>
|