Dynamic Threshold messages when using the java command line interface

Document ID : KB000109435
Last Modified Date : 02/08/2018
Show Technical Document Details
Issue:
Receiving the following output from an attempt to set up a dynamic threshold.

../../../jre/jre7/bin/java -cp ".:lib/*" com.nimsoft.threshold.cmd.ThresholdSetter -user administrator -pwd XXXXXXX -probe "/domain/hub/robot/baseline_engine" -id M3D3D0C3Z572861FB016B50D0E960FE3C  -threshType dynamic -type stddev -o GE -level1 -1000  -subsysId 1.1.1.2
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/prd/xim3/CA/nimsoft/probes/slm/baseline_engine/lib/slf4j-log4j12-1.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/prd/xim3/CA/nimsoft/probes/slm/baseline_engine/lib/log4j-slf4j-impl-2.5.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]

Cannot tell if these messages are an "FYI" or if this means the command was unsuccessful.
Environment:
UIM 8.51
baseline_engine 2.76
Cause:
The baseline_engine probe was upgraded to the 2.76 version available with UIM 8.51 from a version available with an earlier UIM release where the baseline_engine used the slf4j-log4j12-1.6.2.jar file.  On an upgrade, the installation of the baseline_engine probe adds new jar files but will not remove old jjar files that the probe no longer uses.

Despite the appearance of these SLF4J messages, the dynamic threshold change is correctly updated in the baseline_engine threshold.cache.zip file found in the probe's cache_dir directory.
Resolution:
If the 2.76 baseline_engine probe is deployed, it is possible to safely delete or rename the slf4j-log4j12-1.6.2.jar  found in the <installPath>/nimsoft/probes/slm/baseline_engine/lib directory.

The other option is to follow these steps to assure that only the 2.76 baseline_engine jar files are installed in the probe's lib directory:

1. Deactivate the baseline_engine probe
2. Rename the baseline_engine/lib directory
3. Redeploy the 2.76 version of the baseline_engine probe to this hub. This will recreate the lib directory and populate it with the current set of baseline_engine jar files
4. Activate the baseline_engine probe again