Change custom jar numbering in classpath.conf
If you had a custom configuration for the classpath.conf file in a version prior to IXIA CCMS 6.2, you might need to update the values used for numbering the custom jar files.
Prior to IXIA CCMS 6.2, the template file classpath.conf.orig in the %OutputGenDir%/conf/client/ directory suggests using 100 to start numbering your custom jars to be added to IXIA CCMS Output Generator's classpath.
However, in IXIA CCMS 6.2 there are more jar files in the standard classpath.conf file in %OutputGenDir%/conf/. Now the jars defined in %OutputGenDir%/conf/client/classpath.conf conflict with the jars defined in %OutputGenDir%/conf/classpath.conf causing CCMS Output Generator to have an error:
INFO | 2020/07/06 14:12:41 | WrapperSimpleApp Error: Encountered an error running main:
INFO | 2020/07/06 14:12:41 | WrapperSimpleApp Error: Encountered an error running main:
INFO | 2020/07/06 14:12:41 | WrapperSimpleApp Error: java.lang.NoClassDefFoundError: org/slf4j/spi/LocationAwareLogger
INFO | 2020/07/06 14:12:41 | WrapperSimpleApp Error: at java.lang.ClassLoader.defineClass1(Native Method)
INFO | 2020/07/06 14:12:41 | WrapperSimpleApp Error: at java.lang.ClassLoader.defineClass(ClassLoader.java:756)To avoid conflicts, you must start the %OutputGenDir%/conf/client/classpath.conf counter with a higher number, such as 200.
To start the counting at a higher number: