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 » Soap Request Problems

Post new topic  Reply to topic
 Soap Request Problems « View previous topic :: View next topic » 
Author Message
momo_mac
PostPosted: Tue Sep 08, 2009 8:01 am    Post subject: Soap Request Problems Reply with quote

Newbie

Joined: 08 Sep 2009
Posts: 3

When trying to invoke an external web service i am repeatingly getting this error. Nothing I try is working, does anybody have any idea? Its coming out of the failure point of the node. Heres the exceptions.

ExceptionList

RecoverableException

File:CHARACTER:/build/S610_P/src/DataFlowEngine/ImbDataFlowNode.cpp
Line:INTEGER:957
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmTryCatchNode
Name:CHARACTER:cis/service/custdata/CustomerAddReq#FCMComposite_1_12.cis/service/custdata/CustomerProfileReq#FCMComposite_1_4
Label:CHARACTER:cis.service.custdata.CustomerAddReq.CustomerProfileReq.TryCatch

Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException

File:CHARACTER:/build/S610_P/src/DataFlowEngine/ImbComputeNode.cpp
Line:INTEGER:464
Function:CHARACTER:ImbComputeNode::evaluate
Type:CHARACTER:ComIbmComputeNode

Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException

File:CHARACTER:/build/S610_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp
Line:INTEGER:602
Function:CHARACTER:SqlStatementGroup::execute
Type:CHARACTER:ComIbmComputeNode

Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2488
Text:CHARACTER:Error detected, rethrowing
Insert
Type:INTEGER:5
Text:CHARACTER:cis.utils.generateFault.Main
Insert
Type:INTEGER:5
Text:CHARACTER:35.6
Insert
Type:INTEGER:5
Text:CHARACTER:THROW EXCEPTION MESSAGE pError VALUES( 'Exception : ', CAST(pError AS CHARACTER), pText);

UserException
File:CHARACTER:/build/S610_P/src/DataFlowEngine/ImbRdl/ImbRdlThrowExceptionStatements.cpp
Line:INTEGER:224
Function:CHARACTER:SqlThrowExceptionStatement::execute
Type:CHARACTER:ComIbmComputeNode

Catalog:CHARACTER:BIPv610
Severity:INTEGER:1
Number:INTEGER:3701
Text:CHARACTER:User generated exception
Insert
Type:INTEGER:5
Text:CHARACTER:Exception :
Insert
Type:INTEGER:5
Text:CHARACTER:3701
Insert
Type:INTEGER:5
Text:CHARACTER:Error Making SOAP JNI Call: Axis2Requester_processResponseMessageSync : Axis2Requester_processResponseMessageSync - org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x14) was found in the prolog of the document. - Frame : 0 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x14) was found in the prolog of the document.| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)| @: org.[/code]
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Sep 08, 2009 8:17 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Firstly, use code tags when posting this sort of thing - makes it much easier to read.

Secondly, have you tried looking at (and looking up) the error message?

Thirdly, if "nothing you try is working" then what have you already tried? There's no point us suggesting things that have already failed to help!
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
momo_mac
PostPosted: Tue Sep 08, 2009 8:51 pm    Post subject: SOAP Request Problems Reply with quote

Newbie

Joined: 08 Sep 2009
Posts: 3

Thanks, i'll use them next time.
Firstly, I tried searching for the error explanation by using the error number 3701 in information center and it is pointing me to database problems.
Secondly, I made a call to the webservice using soapUI and I get the repsonse .So the webservice is working fine when I call it using soapUI.
Back to top
View user's profile Send private message
mgk
PostPosted: Wed Sep 09, 2009 2:53 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

According to the exception you posted, this is the root cause:

"An invalid XML character (Unicode: 0x14) was found in the prolog of the document."

It suggests that the response message may not be valid XML. Can you post the response message here?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
momo_mac
PostPosted: Thu Mar 24, 2011 8:52 am    Post subject: Reply with quote

Newbie

Joined: 08 Sep 2009
Posts: 3

managed to fix the problem.
the message had & characters as part of the payload. No I had to replace the & with & to get it working.

Code:
DECLARE oldBLOB BLOB InputRoot.BLOB.BLOB;      
      DECLARE originalAmp BLOB CAST('&' AS BLOB CCSID 819 ENCODING 273);
      DECLARE targetAmp BLOB CAST('&' AS BLOB CCSID 819 ENCODING 273);
      DECLARE goodNowBadAmp BLOB CAST('&' AS BLOB CCSID 819 ENCODING 273);
      
      DECLARE newBLOB BLOB REPLACE(oldBLOB, originalAmp, targetAmp);
      --Just in case the xml is well formatted!
      SET newBLOB = REPLACE(newBLOB, goodNowBadAmp, targetAmp);      

      CREATE LASTCHILD OF OutputRoot Domain('XMLNSC') PARSE(newBLOB,273,819);   
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Mar 24, 2011 12:27 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Perhaps you might consider using the Properties folder values for the CCSID & Encoding rather than hardcoding them.
You never know, the incoming message might be coded using say CCSID 923.

CCSID 819 = ISO 8859-1 (WET ISO Latin)
CCSID 923 = ISO 8859-15 (add euro sign etc)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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 » Soap Request Problems
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.