| Author |
Message
|
| nikhilsharma |
 Posted: Wed May 06, 2009 1:12 am Post subject: XML Writing Errors have occurred while htting of webservice |
 |
|
Apprentice
Joined: 10 Aug 2007
Posts: 28
|
Hi
I am getting following error while htting of webservice to our flow
BIP5010E: XML Writing Errors have occurred. : BREIBP2.3c28e892-1f01-0000-0080-be038876e0ae: /build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCParser.cpp: 737:
ImbXMLNSCParser::refreshBitStreamFromElementsCommon: ComIbmWSInputNode: MainFlow_VEL_SSA_iCRM_SRCreateService#FCMComposite_1_2
BIP2136E: Source character '2026' in field
'003c004e00530031003a0045006e00760065006c006f007000650020007800
6d006c006e0073003a004e00530031003d00220068007400740070003a002f
002f0073006300680065006d00610073002e0078006d006c0073006f0061007
0002e006f00720067002f0073006f00610070002f0065006e00760065006c006
f00700065002f0022003e003c004e00530031003a0042006f00640079003e00
3c005300520043007200650061007400650052006500730070006f006e0073
006500200078006d006c006e0073003d00220068007400740070003a002f002
f007700770077002e006500780061006d0070006c0065002e006f00720067002
f005300520043007200650061007400650022003e003c005300520045006c006
5006d0065006e00740073003e003c0070005f0075007300650072005f006e0061
006d0065003e004d00430053004b00490047004300480031003c002f0070005f
0075007300650072005f006e0061006d0065003e003c0070005f007400790070
0065005f00760061006c003e004f007500740062006f0075006e0064003c002f00
70005f0074007900700065005f00760061006c003e003c0070005f00730075006
2007400
Flow Description: In our flow HTTPInput Node is used to receive webservice message and HTTPReply Node is used to return a response from the message flow to an HTTP client
Thanks With Regards
[edited by admin for readability]
_________________
Nikhil |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 06, 2009 1:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What's being used as input? Is is valid XML?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed May 06, 2009 1:34 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
From whats been posted I can make out.....
| Code: |
<NS1:Envelope xmlns:NS1="http://schemas.xmlsoap.org/soap/envelope/"><NS1:Body><SRCreateResponse xmlns="http://www.example.org/SRCreate"><SRElements><p_user_name>MCSKIGCH1</p_user_name><p_type_val>Outbound</p_type_val><p_subt |
Unfortunatly I cant see the offending data from the snippet supplied but it could be something to do with an &. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed May 06, 2009 2:49 am Post subject: Re: XML Writing Errors have occurred while htting of webserv |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| nikhilsharma wrote: |
| BIP2136E: Source character '2026' in field ... |
The more interesting part of the error message got truncated; it should continue:
| Quote: |
| ... cannot be converted from Unicode to codepage <???> |
.
The XML message contains a U+2026 character (horizontal ellipsis). The target codepage does not. The XML parser cannot convert the message from Unicode to the target codepage. |
|
| Back to top |
|
|
| nikhilsharma |
| Posted: Wed May 06, 2009 9:51 pm Post subject: |
|
|
Apprentice
Joined: 10 Aug 2007
Posts: 28
|
The Input message is XML message.It's format is not changed by any application.
Input XML Message :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<m:SRCreateRequest xmlns:m="http://www.example.org/SRCreate">
<m:SRElements>
<m:p_user_name>DELCSATUSER1</m:p_user_name>
<m:p_type_val>Billing</m:p_type_val>
<m:p_subtype_val>E - Account Sep/Merger</m:p_subtype_val>
<m:p_cellno>9923005115</m:p_cellno>
<m:p_attribute2>Not Informed</m:p_attribute2>
<m:p_attribute6>Account separation</m:p_attribute6>
<m:p_attribute15>Information Given.Case Closed</m:p_attribute15>
<m:p_created_by_user>DELCSATUSER1</m:p_created_by_user>
<m:p_media>web</m:p_media>
<m:p_create_date>2009-05-04</m:p_create_date>
<m:p_circle_id>0011</m:p_circle_id>
</m:SRElements>
</m:SRCreateRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How should i go about to resolve this error [XML Writing Error]
_________________
Nikhil |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 06, 2009 11:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nikhilsharma wrote: |
| The Input message is XML message. |
Is this the message you're getting, or the message you think you're getting? Or to put it another way, is this XML extracted from the wire as it hits the inbound node, or what the sending application claim they're transmitting?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 07, 2009 12:23 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| How should i go about to resolve this error [XML Writing Error] |
Well, you could start with the basics. You have posted a truncated error message without making any attempt to find out what the full text of the message is, or when it was thrown.
As I keep on saying, the first steps when you get an error are:
- insert Trace nodes
- take a user trace ( using mqsichangetrace, mqsireadlog, mqsiformatlog )
In this case, taking a user trace would reveal that your exception is nothing to do with XML *writing*. It is being reported by the XML writer because the input tree was not ( fully ) parsed before the write started. The user trace will show *all* of the exceptions thrown, and will include the full text of each BIP message.
It is possible that the XMLNSC parser is being given the wrong code page, but it's close enough for most of the parsing to work OK. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu May 07, 2009 1:17 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Vitor wrote: |
Is this the message you're getting, or the message you think you're getting? |
Its definatly different to the message I decoded previously (even the namespace prefix is different).....
and thanks for chopping up that long string.... makes it much easier to respond now! |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu May 07, 2009 8:03 pm Post subject: Re: XML Writing Errors have occurred while htting of webserv |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| nikhilsharma wrote: |
| The Input message is XML |
True perhaps, but irrelevant. The Output message contains an unconvertable character:
| rekarm01 wrote: |
| nikhilsharma wrote: |
| BIP2136E: Source character '2026' in field ... |
The more interesting part of the error message got truncated; it should continue:
| Quote: |
| ... cannot be converted from Unicode to codepage <???>. |
The XML message contains a U+2026 character (horizontal ellipsis). The target codepage does not. |
The output message header's ccsid (Root.Properties.CodedCharSetId) determines what characters are allowed in the output message body.
| nikhilsharma wrote: |
| How should i go about to resolve this error? |
Either fix the output message header's ccsid, or fix the output message body; business requirements will dictate which of the two is wrong.
What was the output message header's ccsid? How was it set? What should it have been?
How was the output message body populated? Where did the offending character(s) come from? Do they belong in the message?
A couple of the more popular ccsids that support a horizontal ellipsis character ('…') are:- ccsid=1208 (UTF-8)
- ccsid=1252 (Windows Latin 1)
|
|
| Back to top |
|
|
| nikhilsharma |
| Posted: Sun May 10, 2009 11:09 pm Post subject: What was the output message header's ccsid? How was it set? |
|
|
Apprentice
Joined: 10 Aug 2007
Posts: 28
|
The input message header's ccsid and the output message header's ccsid are same.
Message Header for input message:
( ['WSRoot' : 0x114b08a70]
(0x01000000:Name ):Properties = ( ['WSPROPERTYPARSER' : 0x114b0f230]
(0x03000000:NameValue):MessageSet = 'MS_SRCreateService' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 273 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = FALSE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2009-05-06 12:38:58.599101' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'SOAP-HTTP' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = 'text/xml; charset=utf-8' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
Message header for output message:
(0x03000000:NameValue):MessageSet = 'MS_SRCreateService' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 273 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = FALSE (BOOLEAN)
I used trace node in the flow, i don't find any unconverted characters in input message as well as in output message.[/b]
_________________
Nikhil |
|
| Back to top |
|
|
|
|
