Wave: How do I prevent Wave startup process wmd.bat /n DEAMONNAME to overwrite my log4j settings? (Doc ID 1025093.1)

Last updated on SEPTEMBER 27, 2006

Applies to:

Oracle Java CAPS JMS Grid - Version: 5.1.1 and later
Information in this document applies to any platform.

Symptoms

How do I prevent Wave startup process wmd.bat /n DEAMONNAME to overwrite my log4j settings?
The above log4j settings work if you put it in daemon.cfg file, but you never know when it is going to be overwritten by Wave startup process.

How do I make my desired log4j settings permanent? I do not want to keep track of unwanted log4j changes.

It seems after shutdown or restart and some parameters changes Wave could drop my log4j settings and use its own default pattern which is impossible to correlate with application timestamp logging.

There the following files:

...\properties\overrideprops.cfg
...\properties\spiritsoftlog4j.properties
...\properties\log4j.properties

...\wdir\conf\damon_name.cfg

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms