Upstream System Not Getting Response From ASAP Due To Invalid Characters Error (Doc ID 815978.1)

Last updated on SEPTEMBER 06, 2017

Applies to:

Oracle Communications ASAP - Version 4.7.2 to 4.7.2 [Release 4.7]
Information in this document applies to any platform.
***Checked for relevance on 14-MAY-2012***
***Checked for relevance on 25-OCT-2013***
***Checked for relevance on 02-APR-2015***
***Checked for relevance on 06-SEP-2016***

Symptoms

Users are noticing unknown control characters sourced from the Network Element, causing problems in JSRP communication with upstream. The ASAP Server sends results of Order Activation status to upstream system MetaSolv Solution (M6) using a JMS Topic (XVTxxxx). M6 failed to receive responses, an exception below was noted in Weblogic server:

<04-Apr-2009 2:41:16,483 EST AM> <ERROR> <srp.MessageSender> <Thread-17> <Failed to serialize XML
java.io.IOException: The character '^H' is an invalid XML character
at weblogic.apache.xml.serialize.BaseMarkupSerializer.fatalError(BaseMarkupSerializer.java:1889)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.surrogates(BaseMarkupSerializer.java:1561)
at weblogic.apache.xml.serialize.XMLSerializer.printText(XMLSerializer.java:1327)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.characters(BaseMarkupSerializer.java:1413)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1076)
at weblogic.apache.xml.serialize.XMLSerializer.serializeElement(XMLSerializer.java:1103)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1239)
at weblogic.apache.xml.serialize.XMLSerializer.serializeElement(XMLSerializer.java:1103)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1239)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1307)
at weblogic.apache.xml.serialize.BaseMarkupSerializer.serialize(BaseMarkupSerializer.java:501)
at com.mslv.asap.oss.activation.XMLReply.serializeDOM(XMLReply.java:368)
at com.mslv.asap.oss.activation.XMLReply.buildEventResponse(XMLReply.java:151)
at com.mslv.asap.activation.srp.MessageSender.publishEvent(MessageSender.java:333)
at com.mslv.asap.oss.activation.event.EventHandler.run(EventHandler.java:193)

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms