From this, it appears that there is a serialized object, maybe JAXB, that is being reanimated and the class "PrintService" has been altered at the byte code level, more than likely by the autoprobe, which makes the class incompatible with the serialized object form.

We have attempted to skip the /javax/print/PrintService class, but that had no impact.

On review of the autoprobe log, have not been able to locate the actual parent, deep inheritance or dynamic instrumented class that might be causing the binary incompatibilities.