This error is fairly rare.  It usually appears to the user as an error like the following


The brief error text in the picture is not very descriptive, but if you open up the Java Stack Trace (or check the DataSplice server logs), then you might find a string like the one in the title of this document.

"Caused by: java.lang.VerifyError: JVMCFRE107 offset out of range in jump bytecode; class=psdi/app/workorder/WO_Skel"


In this example, the WO_Skel.class file provided by Maximo (maybe compiled before a maximo upgrade?) does not match with the actual WO.class file provided by Maximo.


Solution


1) Rebuild _stub files using the exact same java version as the Maximo application.  (this process is documented here:  http://support.datasplice.com/support/solutions/articles/1000241588-recompiling-the-maximo-stub-files)

2) Delete _skel.class files from DataSplice and Maximo businessobjects classes.

3) Re-build deployment ear/jars.

4) Redeploy the new ears.

5) Copy updated Jars to Datasplice for use in the MaximoPlugin classpath.


Agent Notes:  Refer to 4786.