When turning on sql trace via the CSA if the filename on an appender has an unsupported character this can cause the entries in the logger.xml file to be removed

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Issue:

When turning on sql trace via the Clarity System Administration (CSA) application (a.k.a. NSA), if the filename on an appender has an unsupported character this can cause the entries in the logger.xml file to be removed.

Steps to Reproduce:

Assumption: Detect 'Log Configuration Changes Automatically' is checked

1. Log into the CSA
2. Select the Server > Click on Logs > Edit Configuration
3. Select Appender XML and click on Copy Appender
4. Edit the copied appender and replace copy with myuser01 (xml_myuser01)
5. Edit the 'File' change the name to ../logs/trace.myuser01.xml
6. Click Save
7. Click Add Category
8. In 'Appender' field select xml_myuser01
9. In 'Other Name' field enter: trace.server.user.myuser01
10. Change 'Priority' to All
11. Click Save
12. Note: you see the message indicating the trace is turned on
13. Bring up another browser session
14. Come back to the CSA which is still on the Edit Configuration view
15. Change 'Priority' from All to Warn
16. Click Save

Expected Result: To get a warning message indicating the filename is invalid  

Actual Result: The only category and appender left is the one you created for the sql trace - all other entries are removed  

Cause:

Caused by CLRT-68400

 

Resolution:

Tested, verified and closed as 'cannot reproduce' on CA Clarity PPM 13.2

Workaround:

Restore the logger.xml file from <install>/.setup/templates/config to the <install>/config directory
In the CSA on the Edit Configuration view click on Reset to restore the values from the logger.xml file

 

Environment

Release: ESPCLA99000-13.1-Clarity-Extended Support Plus
Component: