Topic
1 reply Latest Post - ‏2013-02-05T02:20:49Z by SystemAdmin
SystemAdmin
SystemAdmin
289 Posts
ACCEPTED ANSWER

Pinned topic Error serializing BO / SAXParseException: An invalid XML character

‏2013-01-18T11:46:04Z |
Hi,

I am using WPS/WESB 7.5 with jms/mq export and using default data format = SOAP, default message format = Byte.

The message comes to MQ is having ccsid = 1208, but WESB throws following exception :

1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save User options passed were:
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: FORMATTED Value: false
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save All options used were:
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: ENCODING Value: UTF-8
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: ANY_SIMPLE_TYPE Value: org.eclipse.emf.ecore.impl.EClassImpl@49184918 (name: EDataObjectSimpleAnyType) (instanceClassName: null) (abstract: false, interface: false)
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: FORMATTED Value: false
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: ANY_TYPE Value: org.eclipse.emf.ecore.impl.EClassImpl@49074907 (name: EDataObjectAnyType) (instanceClassName: null) (abstract: false, interface: false)
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: EXTENDED_META_DATA Value: com.ibm.ws.bo.BOExtendedMetaData@56175617
1/18/13 12:40:41:005 CET 0000008b BOXMLSerializ E com.ibm.ws.bo.service.BOXMLSerializerImpl save Key: USE_CACHED_LOOKUP_TABLE Value: org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl$Lookup@7e347e34
1/18/13 12:40:41:005 CET 0000008b FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\AppServer\profiles\qbpmaps\logs\ffdc\server1_38503850_13.01.18_12.40.41.0056464316679593533359.txt java.lang.RuntimeException caught trying to serialize BO {http://www.ibm.com/websphere/sibx/smo/v6.0.1, DocumentRoot} 214
1/18/13 12:40:41:021 CET 0000008b FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\AppServer\profiles\qbpmaps\logs\ffdc\server1_38503850_13.01.18_12.40.41.0051817877853137845111.txt com.ibm.wsspi.sibx.mediation.flow.ejb.MediationFlowBean.invokeRequestFlow 1:298:1.34
1/18/13 12:40:41:037 CET 0000008b MediationFlow E CWSXM1025E: An unexpected exception occurred when the flow was called: Error serializing BO {http://www.ibm.com/websphere/sibx/smo/v6.0.1, DocumentRoot}
1/18/13 12:40:41:037 CET 0000008b MFCImplementa E CWSXM0202E: An unexpected exception occurred when processing mediation flow for component PreProcessorMed in module TestMod: CWSXM1025E: An unexpected exception occurred when the flow was called: Error serializing BO {http://www.ibm.com/websphere/sibx/smo/v6.0.1, DocumentRoot}
1/18/13 12:40:41:037 CET 0000008b FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\AppServer\profiles\qbpmaps\logs\ffdc\server1_38503850_13.01.18_12.40.41.0374858345198972621059.txt com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage 1295
1/18/13 12:40:41:037 CET 0000008b FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\AppServer\profiles\qbpmaps\logs\ffdc\server1_38503850_13.01.18_12.40.41.0372616891358569502503.txt com.ibm.wsspi.sca.jms.inbound.MQJMSInboundImpl 0x03
1/18/13 12:40:41:068 CET 0000008b FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\IBM\WebSphere\AppServer\profiles\qbpmaps\logs\ffdc\server1_38503850_13.01.18_12.40.41.0374610630263501264843.txt com.ibm.ws.container.binding.jms.TransactionalMessageEndpoint.invokeBusinessMethod 383
1/18/13 12:40:41:115 CET 0000008b SibMessage W [:] CWSJY0003W: JMSCC0109: A message driven bean threw a runtime exception '
Message : com.ibm.websphere.sca.ServiceRuntimeException: CWSXM0202E: An unexpected exception occurred when processing mediation flow for component PreProcessorMed in module TestMod: CWSXM1025E: An unexpected exception occurred when the flow was called: Error serializing BO {http://www.ibm.com/websphere/sibx/smo/v6.0.1, DocumentRoot}: caused by: com.ibm.wsspi.sibx.mediation.flow.MediationRuntimeException: CWSXM1025E: An unexpected exception occurred when the flow was called: Error serializing BO {http://www.ibm.com/websphere/sibx/smo/v6.0.1, DocumentRoot}
Class : class com.ibm.websphere.sca.ServiceRuntimeException

The FFDC file shows following error:

FFDC Exception:java.lang.RuntimeException SourceId:com.ibm.ws.sibx.scax.mediation.engine.utils.trace.SIBXTraceUtil.printMessage ProbeId:1:470:1.27
java.lang.RuntimeException: An error occurred while parsing native data: The error message is: commonj.connector.runtime.DataBindingException: commonj.connector.runtime.DataBindingException: commonj.connector.runtime.DataHandlerException: javax.xml.soap.SOAPException: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x52) was found in the prolog of the document. Message being parsed: .
Caused By: commonj.connector.runtime.DataBindingException: commonj.connector.runtime.DataBindingException: commonj.connector.runtime.DataHandlerException: javax.xml.soap.SOAPException: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x52) was found in the prolog of the document. Message being parsed:

Please help!!
Updated on 2013-02-05T02:20:49Z at 2013-02-05T02:20:49Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    289 Posts
    ACCEPTED ANSWER

    Re: Error serializing BO / SAXParseException: An invalid XML character

    ‏2013-02-05T02:20:49Z  in response to SystemAdmin
    Hi,

    Please try with function selector as JMS message type selector,Default data format as UTF8XMLDataHandler and Default message type as Byte.

    Cheers,
    Sachin