Multiple SLF4J Bindings found in New PAM Installation

Products

• CA Process Automation Base

Issue/Introduction

When installing a new installation of PAM 4.3, the following errors are seen in the c2o.log:

2022-12-08 12:21:51,693 ERROR [STDERR] [           main] SLF4J: Class path contains multiple SLF4J bindings.
2022-12-08 12:21:51,709 ERROR [STDERR] [           main] SLF4J: Found binding in [vfszip:/C:/Program Files/CA/PAM/server/c2o/ext-deploy/slf4j-log4j12-1.7.2.jar/org/slf4j/impl/StaticLoggerBinder.class]
2022-12-08 12:21:51,709 ERROR [STDERR] [           main] SLF4J: Found binding in [vfszip:/C:/Program Files/CA/PAM/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class]
2022-12-08 12:21:51,709 ERROR [STDERR] [           main] SLF4J: Found binding in [vfszip:/C:/Program Files/CA/PAM/server/c2o/ext-lib/activemq-all-5.15.11.jar/org/slf4j/impl/StaticLoggerBinder.class]
2022-12-08 12:21:51,709 ERROR [STDERR] [           main] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2022-12-08 12:21:51,709 ERROR [STDERR] [           main] SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Environment

Release : 4.3 and higher

Resolution

These errors can be safely ignored and should not cause any further issues.

 

 

Additional Information

If the second PAM node can't start after installation, with the messages as mentioned above, and the activemq.log in PAM-activemq-folder\data displays

Starting ActiveMQ with JAVA_HOME->""c:\program files\java\jdk-11"
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/activemq/ActiveMQConnectionFactory

then please follow these steps

• rename PAM-activemq-folder\data\tmp to old_tmp
• copy the tmp from a working node to PAM-activemq-folder\data and start PAM

If these steps don't work for you, please contact Broadcom Support.