IBM Support

Custom Java applications running on Java 1.6 JVMs with CPE 5.5.3 client libraries see TRANSPORT_WSI_SERIALIZATION_ERROR

Troubleshooting


Problem

Beginning with FileNet Content Platform Engine (CPE) 5.5.1, client Java applications using a Java 1.6  JVM are not supported.  However, custom applications using CPE 5.5.1 and 5.5.2 client libraries may continue to work with a 1.6 JVM.  As of CPE 5.5.3, client applications using a 1.6 JVM may encounter TRANSPORT_WSI_SERIALIZATION_ERROR messages when connecting using the web services transport.

Symptom

When connecting to the CPE using the web services transport, the error stack will be similar to:
com.filenet.api.exception.EngineRuntimeException: FNRCT0043E: TRANSPORT_WSI_SERIALIZATION_ERROR: Error serializing a web services instance of <init>. Cannot find StAX XML parser XLXP in this environment. Check application configuration and product documentation.  You may need to put xlxpScanner.jar and xlxpScannerUtils.jar on your classpath. You may be using a faulty copy of the IBM XLXP parser from a classloader issue or other circumstance. Duration 171 milliseconds.
    at com.filenet.apiimpl.wsi.serialization.Util.ereOrIoe_common(Util.java:855)
    at com.filenet.apiimpl.wsi.serialization.TokenWriterNst.initFactory(TokenWriterNst.java:60)
    at com.filenet.apiimpl.wsi.serialization.TokenWriterNst.<init>(TokenWriterNst.java:88)
    at com.filenet.apiimpl.wsi.ServiceSessionNst.cReqRespPath(ServiceSessionNst.java:334)
    at com.filenet.apiimpl.wsi.ServiceSessionNst.getObjects(ServiceSessionNst.java:187)
    at com.filenet.apiimpl.util.SessionHandle.getObjects(SessionHandle.java:346)
    at com.filenet.apiimpl.core.Session.callGetObjects(Session.java:132)
    at com.filenet.apiimpl.core.Session.executeGetObject(Session.java:340)
    at com.filenet.apiimpl.core.Session.getObject(Session.java:354)
    at com.filenet.apiimpl.core.IndependentObjectImpl.getObject(IndependentObjectImpl.java:147)
    at com.filenet.apiimpl.core.IndependentObjectImpl.refresh(IndependentObjectImpl.java:155)
    at com.filenet.api.core.Factory$Domain.fetchInstance(Factory.java:8693)
    at com.filenet.framework2.mputil.AuthenticationHelper.authenticate(AuthenticationHelper.java:441)
    at com.filenet.framework2.mputil.MethodInvoker.run(MethodInvoker.java:195)
    at java.security.AccessController.doPrivileged(AccessController.java:448)
    at javax.security.auth.Subject.doAs(Subject.java:573)
    at com.filenet.framework2.mputil.MethodInvoker.invokeMethod(MethodInvoker.java:150)
    at com.filenet.framework2.mputil.AuthenticatedTestScript.invokeTestMethod(AuthenticatedTestScript.java:77)
    at com.filenet.framework2.controller.Controller.run(Controller.java:432)
    at com.filenet.framework2.controller.Controller.main(Controller.java:1303)
Caused by: java.lang.NoSuchMethodError: javax/xml/stream/XMLOutputFactory.newFactory()Ljavax/xml/stream/XMLOutputFactory;
    at com.filenet.apiimpl.wsi.serialization.TokenWriterNst.initFactory(TokenWriterNst.java:56)
    ... 18 more
 
This error can occur under various conditions, and may be intermittent.  When a custom application with CPE 5.5.3 client libraries uses a 1.6 JVM, the errors will persist.

Document Location

Worldwide

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.5.3","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
28 April 2025

UID

ibm10957387

Page Feedback