Hi,

Whenever i modify the log4j.properties i have to restart the server.

Is there are way i can do this without having to restart the server.

Thanks in advance,

Gamad

Gamad,

I’m not sure how you are using log4j, but I put together a log4j logging IS package some time back that reads properties from a properties file. I think I remember that you can re-run the initialization service to reload a log4j properties file, but I could be wrong.

You can find my example and a newer one that works with JDK 1.4 logging in the WM Users shareware area.

[url=“wmusers.com”]wmusers.com

Mark

Hi Mark,

Your article and code did help.

Thanks a bunch,

Gamad

Hi Mark,

The jdk1.4 version of logger zip seems to be corrupt.

Regards
Ashok

This package works very well. I just plopped the log4j into the IntegrationServer\lib\jars directory as mentioned in this package and changed the Pipeline on the logInit to specify my log4j.properties preference… Reloaded the package & all was well!

Thanks, Mark!
-Rahul

Rahul,

Glad the old logging utility is still helping out!

Mark

Hi what version IS did this work with? Your post is from Feb, so I am hoping you are talking about version 6.*…

Thanks

Hi Mark,
I have been able to implement log4j for logging except one anomaly that I see with respect to the deletion of loggers.

I see that the logMessage service has a “success” for a Logger that was removed from the log4j.properties file. I did run the load properties service post deletion of the logger.

Also, below are the extended settings that were put in place:

watt.LogManagement.appslog.directory= for eg IS/logs/Log4jLogs
watt.LogManagement.working.directory= for eg IS/Log4j
watt.LogManagement.working.status=true

How do we clear the non-existent loggers from the memory?

Thanks
Suhail