ap.SoapFault

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • soapFault exception
    via by 3004,
    • ap.SoapFault: b <n <-- bad character Error at line:18 col:4 '<' expected [?! -- [CDATA[ ] at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseException(SAXElementFactory.java:60) at weblogic.xml.babel.parsers.StreamParser.streamParseSome(StreamParser.java:130) at weblogic.xml.babel.parsers.BabelXMLEventStream.parseSome(BabelXMLEventStream.java:46) at weblogicx.xml.stream.SubEventStream.parseSome(SubEventStream.java:48) at weblogicx.xml.stream.SubElementEventStream.parseSome(SubElementEventStream.java:38) at weblogicx.xml.stream.SubEventStream.parseSome(SubEventStream.java:48) at weblogicx.xml.stream.SubElementEventStream.parseSome(SubElementEventStream.java:38) at weblogicx.xml.stream.XMLEventStreamBase.hasNext(XMLEventStreamBase.java:135) at weblogicx.xml.stream.helpers.TextBuilder.process(TextBuilder.java:23) at weblogic.soap.codec.SoapEncodingCodec.decode(SoapEncodingCodec.java:194) at weblogic.soap.codec.SoapEncodingCodec.decode(SoapEncodingCodec.java:145) at weblogic.soap.codec.CodecFactory.decode(CodecFactory.java:66) at weblogic.soap.codec.Operation.read(Operation.java:97) at weblogic.soap.codec.SoapMessage.readOperation(SoapMessage.java:200) at weblogic.soap.codec.SoapMessage.read(SoapMessage.java:130) at weblogic.soap.WebServiceProxy.receive(WebServiceProxy.java:480) at weblogic.soap.WebServiceProxy.invoke(WebServiceProxy.java:431) at weblogic.soap.SoapMethod.invoke(SoapMethod.java:186) at CountClient.main(CountClient.java:60)
    No Bugmate found.