Description:
Tomcat goes into an infinite loop and throws the error,  "java.lang.NoSuchMethodError: com.tibco.pe.plugin.TraceMessage.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)".

In BusinessWorks 5.6.2, there is the TraceMessage class in both the engine.jar and mapper.jar. The version in mapper.jar is the correct one and the version in engine.jar is the wrong one.

Symptoms:
In BusinessWorks(TM) BW 5.6.2 we have TraceMessage class in both “engine.jar” and “mapper.jar”.The version in mapper.jar is the correct one and the version in engine.jar the wrong one.

When BW is deployed in TIBCO BusinessWorks(TM) Collaborator (BWC) world it is deployed in a TOMCAT container setup. In this all BW jars are copied to shared/lib folder and TOMCAT loads all jars alphabetically. So it is loading engine.jar first which has the wrong version.
Cause:
In BusinessWorks 5.6.2 there is the TraceMessage class in both “engine.jar” and “mapper.jar”. The version in mapper.jar is the correct one and the version in engine.jar is the incorrect one.

When BW is deployed in the TIBCO BusinessWorks Collaborator environment, it is deployed in a Tomcat container. All BW JARs are copied to shared/lib folder and Tomcat loads the JARs alphabetically so it loads the engine.jar first which has the incorrect version.

Tomcat goes into an infinite loop and throws the error, "java.lang.NoSuchMethodError: com.tibco.pe.plugin.TraceMessage.

The workaround is to rename mapper.jar to "amapper.jar" so that it gets loaded first.