|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Error serializing BO com.ibm.wsspi.sca.message.impl.Document |
« View previous topic :: View next topic » |
Author |
Message
|
pandeg |
Posted: Wed Sep 21, 2016 7:31 am Post subject: Error serializing BO com.ibm.wsspi.sca.message.impl.Document |
|
|
Disciple
Joined: 21 Oct 2014 Posts: 195
|
Hi, We are getting below exception in the AppTarget of the WPS application. is it something related to IBM library not gettting loaded during server startip. How to identify and fix this issue.
javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: Error serializing BO com.ibm.wsspi.sca.message.impl.DocumentRootImpl@e980e98 (mixed: [soap:envelope=com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl@54315431 (anyAttribute: null)], encodingStyle: null, mustUnderstand: <unset>, relay: <unset>, role: null)
at javax.ejb.EJBException.<init>(EJBException.java:6
at com.ibm.wsspi.container.binding.sca.remote.ServiceRemoteBean_81545.processMessageBytes(Unknown Source)
at com.ibm.wsspi.container.binding.sca.remote.EJSRemoteCSLConvertTypeBMessageToTypeBString_a742a90a.processMessageBytes(EJSRemoteCSLConvertTypeBMessageToTypeBString_a742a90a.java)
at com.ibm.wsspi.container.binding.sca.remote._EJSRemoteCSLConvertTypeBMessageToTypeBString_a742a90a_Tie.processMessageBytes(_EJSRemoteCSLConvertTypeBMessageToTypeBString_a742a90a_Tie.java)
at com.ibm.wsspi.container.binding.sca.remote._EJSRemoteCSLConvertTypeBMessageToTypeBString_a742a90a_Tie._invoke(_EJSRemoteCSLConvertTypeBMessageToTypeBString_a742a90a_Tie.java)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)
at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: java.lang.RuntimeException: Error serializing BO com.ibm.wsspi.sca.message.impl.DocumentRootImpl@e980e98 (mixed: [soap:envelope=com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl@54315431 (anyAttribute: null)], encodingStyle: null, mustUnderstand: <unset>, relay: <unset>, role: null)
at com.ibm.ws.bo.service.BOXMLSerializerImpl.save(BOXMLSerializerImpl.java:569)
at com.ibm.ws.bo.service.BOXMLSerializerImpl.writeXMLDocumentWithOptions(BOXMLSerializerImpl.java:629)
at com.ibm.ws.sca.internal.sdo.impl.BOXMLSerializerDelegatorImpl.save(BOXMLSerializerDelegatorImpl.java:233)
at com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.save(XMLFileServiceImpl.java:447)
at com.ibm.wsspi.sca.sdo.XMLFileService$1.save(XMLFileService.java:96)
at com.ibm.wsspi.sca.sdo.XMLFileService$1.save(XMLFileService.java:89)
at com.ibm.ws.sca.internal.message.impl.EMFMessageSerializer.save(EMFMessageSerializer.java:7
at com.ibm.ws.sca.internal.message.impl.EMFMessageSerializer.save(EMFMessageSerializer.java:166)
at com.ibm.ws.sca.internal.binding.handler.SCAExportMessageHelper.processMessageBytes(SCAExportMessageHelper.java:167)
at com.ibm.ws.sca.internal.binding.handler.spi.impl.ExportSCAInvoker.invoke(ExportSCAInvoker.java:53)
at com.ibm.ws.container.binding.classicsca.ejb.EJBDefaultBindingServiceProvider$EJBDefaultBindingServiceInvoker.invoke(EJBDefaultBindingServiceProvider.java:57)
at com.ibm.ws.container.binding.classicsca.ejb.EJBDefaultBindingServiceProvider$EJBDefaultBindingServiceInvoker.invoke(EJBDefaultBindingServiceProvider.java:40)
at com.ibm.ws.container.binding.ejb.BaseContainerBeanImpl.invoke(BaseContainerBeanImpl.java:54)
... 13 more
Caused by: java.lang.RuntimeException: An invalid XML character (Unicode: 0x1) was found in the element content: |
|
Back to top |
|
 |
Vitor |
Posted: Wed Sep 21, 2016 7:47 am Post subject: Re: Error serializing BO com.ibm.wsspi.sca.message.impl.Docu |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
pandeg wrote: |
is it something related to IBM library not gettting loaded during server startip. |
I doubt it.
pandeg wrote: |
Code: |
javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: Error serializing BO com.ibm.wsspi.sca.message.impl.DocumentRootImpl@e980e98 (mixed: [soap:envelope=com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl@54315431 (anyAttribute: null)], encodingStyle: null, mustUnderstand: <unset>, relay: <unset>, role: null) |
|
sounds more like bad data to me. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
pandeg |
Posted: Wed Sep 21, 2016 8:00 am Post subject: Re: Error serializing BO com.ibm.wsspi.sca.message.impl.Docu |
|
|
Disciple
Joined: 21 Oct 2014 Posts: 195
|
Quote: |
sounds more like bad data to me. |
Thanks , does this needs to be filter by application code or we need to do
server restart everytime (that's what we are doing so far to fix it temporarily.) |
|
Back to top |
|
 |
Vitor |
Posted: Wed Sep 21, 2016 8:02 am Post subject: Re: Error serializing BO com.ibm.wsspi.sca.message.impl.Docu |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
pandeg wrote: |
Quote: |
sounds more like bad data to me. |
Thanks , does this needs to be filter by application code or we need to do
server restart everytime (that's what we are doing so far to fix it temporarily.) |
Fixing a problem by restarting the server is never the right plan.
Nor is writing application code to ignore ("filter") the error. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
pandeg |
Posted: Wed Sep 21, 2016 8:07 am Post subject: Re: Error serializing BO com.ibm.wsspi.sca.message.impl.Docu |
|
|
Disciple
Joined: 21 Oct 2014 Posts: 195
|
Quote: |
Nor is writing application code to ignore ("filter") the error. |
I will have to check with developer what is this invalid XML character (Unicode: 0x1) in their source file. May be they are not able to parse it.
Also, how can we handle this character in WebSphere Process Server ? |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|