ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP3701E: A Java exception, An invalid XML character

Post new topic  Reply to topic
 BIP3701E: A Java exception, An invalid XML character « View previous topic :: View next topic » 
Author Message
k0deshp
PostPosted: Tue May 08, 2018 7:45 am    Post subject: BIP3701E: A Java exception, An invalid XML character Reply with quote

Newbie

Joined: 06 May 2018
Posts: 5

When I am passing the message to SOAP Request node am getting below error:

I understand this is something to do with forming correct SOAP Request but not able to pinpoint the issue in the code.

My flow:

SOAPInput->Soap Extract->Compute->SOAPRequest->Compute->SOAPReply


**************************************

BIP3701E: A Java exception was thrown whilst calling the Java JNI method ''Axis2Requester_processRequestMessageNonSoap''. The Java exception was ''org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x50) was found in the prolog of the document.''. The Java stack trace was ''Frame : 0 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x50) was found in the prolog of the document.
**************************************

Compute node code looks like this:

CALL CopyMessageHeaders();
--CALL CopyEntireMessage();

SET OutputLocalEnvironment.Destination.SOAP.Request.Transport.HTTP.WebServiceURL = 'http://xxx.com:port/apps/try/GetPromoPriceService';

SET OutputRoot.SOAP.Context.Namespace.(SOAP.NamespaceDecl)xmlns:soapenv = soapenv;
SET OutputRoot.SOAP.Context.Namespace.(SOAP.NamespaceDecl)xmlns:try = try;
SET OutputRoot.SOAP.Body.try:ItemDescPriceRequest.try:ItemSKU = '123';
SET OutputRoot.SOAP.Body.try:ItemDescPriceRequest.try:Price = 2.0;
SET OutputRoot.SOAP.Body.try:ItemDescPriceRequest.try:Description = 'First Sellable Item for Promotional purpose';

*************************************************

What am I doing wrong here?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue May 08, 2018 7:58 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

sounds like a ccsid problem to me. Did you create an xml declaration and did you set the encoding there to UTF-8 ? Add in the OutputRoot.Properties setting the ccsid to 1208 and you should be good.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
k0deshp
PostPosted: Thu May 10, 2018 11:12 am    Post subject: Reply with quote

Newbie

Joined: 06 May 2018
Posts: 5

I had wrongly set the urlpath in HTTP Transport properties in SOAP input node of calling webservice from SOAPRequest Node.
I set HTTP Transport as http://<hostname:port>/<webservicenamewithpath>

I modified it to <webservicenamewithpath> it started working fine
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP3701E: A Java exception, An invalid XML character
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.