SLF4J: Class path contains multiple SLF4J bindings

book

Article ID: 221138

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Try to deploy/redeploy a mar file by command line (powershell). Following WARNING messages are received:

PS C:\Users\USER> E:\SomePath\CA\DevTest\bin\vsemanager.exe --username=xxx --password=yyy --redeploy "E:\PathToThe\Specific.mar"
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/E:/SomePath/CA/DevTest/lib/shared/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/E:/SomePath/CA/DevTest/lib/shared/slf4j-simple-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Locale: en_US
Setting System.out and System.err to: Cp1252
LISA_HOME set to E:\SomePath\CA\DevTest\
Config server url not provided. Using properties from install location
Config server url not provided. Using properties from install location
DevTest temporary directory is C:\Users\USER\lisatmp_10.6.0
Configuring logging from 'E:\SomePath\CA\DevTest\logging.properties'
DevTest Solutions, Copyright (c) 2002-2021 Broadcom, All rights reserved.
DevTest Virtual Service Environment Manager - The Command Line Tool for Managing VSEs.
DevTest Solutions Version :: 10.6.0 (10.6.0.1011)

Mar file was correctly deployed.

To remove this warning, deleted/moved one of the libraries (slf4j-simple-1.7.12.jar). 

Is it correct to do this or if there is an other solution?

Cause

This message says that, the same class file is resolved in 2 different JARs.

Environment

Release : 10.6

Component : CA Service Virtualization

Resolution

 

These messages can be safely ignored. 

It is recommended NOT to alter the contents of the DevTest library folders unless it has been suggested by product support or other product SME from Broadcom.

Restore the JAR into its original location and restart DevTest components.