Symantec Identity Manager - Debug mode not working correctly, page Logging_v2.jsp

Products

• CA Identity Suite
• CA Identity Manager

Issue/Introduction

We have recently upgraded to 14.4 CP1 CH2 and when we access the logging_v2.jsp page (which was a defect in 14.4 GA, DE509254) it shows that all of the items have state DEBUG.

However, looking at the logs it is not certain that everything is running in DEBUG mode, rather more likely in the ERROR, which is the default for the logging.jsp items.

I can change the state to ERROR, but when I restart IM the state displayed via the logging_v2.jsp page returns to showing DEBUG.  SO DEBUG is the default displayed after a restart (the settings via logging_v2.jsp only last as long as IM is up and revert to default on IM restart.  I thought ERROR was that default).

 

 

Environment

Release : vApp 14.4 GA to CP1 CHF2

Resolution

Configuration Requirements for Log4j2 Loggers
The following additional steps are required for managing log levels in 14.4 in JBoss/WildFly, and WebSphere:

 

For JBoss/WildFly Linux:

Add the following line to <JBoss_bin>/standalone.conf:

JAVA_OPTS="$JAVA_OPTS -DLog4jContextSelector=org.apache.logging.log4j.core.selector.BasicContextSelector"

 

For JBoss/WildFly Windows

Add the following line to <JBoss_bin>/standalone.conf.bat:

JAVA_OPTS="$JAVA_OPTS -DLog4jContextSelector=org.apache.logging.log4j.core.selector.BasicContextSelector"

Restart the Application Server to take effect.

For Virtual Appliance:

cd /opt/CA/VirtualAppliance/custom/IdentityManager
vi jvm-args.conf

add: -DLog4jContextSelector=org.apache.logging.log4j.core.selector.BasicContextSelector

Then issue the aliases to restart while clearing the JMS queue cache:
stop_im
deleteIDMJMSQueue
start_im

Additional Information

In 14.4 GA you will need first install hotfix: DE509254 to see logging_v2.jsp