Troubleshooting Logging Configuration

The following table lists common logging issues and the actions you can take to resolve them:

Issue	Solution
No DEBUG records appear.	Verify the package name and confirm that the application executed the relevant code. Check that the logger level and appender-reference threshold allow DEBUG.
Records appear in the file but not in the console.	Verify that the package logger includes a Console reference with a level that allows the diagnostic records. Changing a package level does not change the root console threshold.
FileLogger cannot be found.	Check whether the logger was added to the console-only EnvironmentArbiter branch. Use only Console in that branch.
Records are duplicated.	Verify that the package logger uses additivity="false" and doesnot forward the same event through the root logger.
The change has no effect after five minutes.	Verify that the process uses the edited file. Check the console for Log4j2 configuration warnings, validate the XML, and restart Open Integration if necessary.
Logging changes affect only some requests.	Verify that every instance handling those requests has the required configuration.
The change disappears after redeployment.	Apply the change through the deployment-managed source or mounted configuration. Files under the deployment target can be replaced during packaging or deployment.