ERROR Unable to create Lookup for jvmrunargs
search cancel

ERROR Unable to create Lookup for jvmrunargs

book

Article ID: 447954

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

You see the following error in the Performance Center (PC) wrapper log on startup in NetOps Performance Management 25.4.9:

INFO | jvm 1 | ####/##/## ##:##:## | ####-##-##T##:##:##.#########Z WrapperSimpleAppMain ERROR Unable to create Lookup for jvmrunargs
INFO | jvm 1 | ####/##/## ##:##:## | java.lang.ClassCastException: class org.apache.logging.log4j.core.lookup.JmxRuntimeInputArgumentsLookup
INFO | jvm 1 | ####/##/## ##:##:## | at java.base/java.lang.Class.asSubclass(Unknown Source)
INFO | jvm 1 | ####/##/## ##:##:## | at org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:##)
INFO | jvm 1 | ####/##/## ##:##:## | at org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:###)
INFO | jvm 1 | ####/##/## ##:##:## | at org.apache.logging.log4j.core.config.AbstractConfiguration.(AbstractConfiguration.java:###)
INFO | jvm 1 | ####/##/## ##:##:## | at org.apache.logging.log4j.core.config.NullConfiguration.(NullConfiguration.java:##)
INFO | jvm 1 | ####/##/## ##:##:## | at org.apache.logging.log4j.core.LoggerContext.(LoggerContext.java:###)

Environment

NetOps Performance Management 25.4.9

Cause

This error is a direct consequence of conflicting Log4j library versions being loaded on the application's classpath.

Resolution

To resolve this issue, you must replace the conflicting Log4j 2.25.3 JAR files with Log4j 2.26.0 JARs.

  1. Locate the following files in the /opt/CA/PerformanceCenter/jetty/lib/ext/ directory:

    • log4j-api-2.25.3.jar
    • log4j-core-2.25.3.jar
    • log4j-slf4j-impl-2.25.3.jar
  2. Replace these files with the Log4j 2.26.0 versions. You can source these JARs from other application library folders, such as:

    • /opt/CA/PerformanceCenter/PC/webapps/pc/WEB-INF/lib/
  3. Restart console service (systemctl restart caperfcenter_console).

Additional Information

Permanent Fix

This issue is officially fixed in release 25.4.10 and higher.