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 » XML Parsing error after Collection node

Post new topic  Reply to topic
 XML Parsing error after Collection node « View previous topic :: View next topic » 
Author Message
ipujals
PostPosted: Tue Feb 12, 2013 3:05 am    Post subject: XML Parsing error after Collection node Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

Hi experts!

I have another bizarre problem.

I am using WMB 8.0.0.1 and a flow which a collector node. It has two input messages, one after a SOAP call and another one after SAP call.

When collection node propagates the collection, SOAP message is well formed, but SAP response returns me the following structure:
- Collection.SAP_RESPONSE.XMLNSC XML Parsing error have occured.

The strange thing is, if I debug flow just before collection node, I can see the SAP_RESPONSE well-formed, and if I make a copy of the SAP_RESPONSE and send it to a MQOutput node, the message is well formed too.

Why is collection node 'destructing' my message?

Thank you very much!
Back to top
View user's profile Send private message
ipujals
PostPosted: Tue Feb 12, 2013 3:48 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

Hi..

I have seen Collection.SAP_RESPONSE.Properties.ContentType has disappeared after collection...

Just before Collection Node and after SAP Response ContetType was text/xml;charset=UTF-8
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Feb 12, 2013 6:13 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

First: you should use Trace nodes, not the interactive debugger.

Second: WMB does not destruct your message. Sometimes the message may not conform exactly to the XSD and if you have validation turned on, the bitstream will be null. Other times, you may have incorrectly configured the node and chosen the wrong operation. Therefore, the node expects a certain response message but receives a different response message.

Third: The WMB product is very robust and well tested. While no software is bug-free, WMB is hardened. If you encounter a problem, your first assumption should be the human is in error, not the product.

Forth: Your lack of knowledge is your greatest stumbling block. Why have you not attended the required training for this product?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
ipujals
PostPosted: Tue Feb 12, 2013 6:40 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

First: I am using it. Only debugging when I found something weird.

Second: It conforms before collection, I have validation turned off, Collection Node has no operation field. Destruct was a way to say it, that's the reason of quoting it.

Third: Of course I assume it is my fault, I know I am a newer here. Butseveral of my posts on this forum ends with a 'it's a bug, wait for the next fixpack'. And it increases when talking about SAP Adapter. Even thoug I have never said in this is post that my problem is because of a bug.

Forth: Your lack of knowledge about myself and my past and present WMB situation, is why this point is disrespectful.

Thank you for helping so kindly to newer users...
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Feb 12, 2013 6:46 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

No disrespect is intended. If your offended, I am sorry.

SAP is one of the more complicated interfaces because it depends so heavily on third party functionality.

Proper use of Trace nodes will yield more information to you more quickly. If you skill-up on using various features of WMB, you won't need to post questions, you will be posting answers instead,

lancelotlinc wrote:
kash3338 wrote:
lancelotlinc wrote:
The interactive debugger is a poor choice here. Try Trace nodes.


Accepted, trace nodes are a good choice, but why do you say interactive debugger as a poor choice? Any specific reason?


Because its hard to keep track of where you are in the flow, and once you pass the problem area in the interactive state, you have to start all over again. Using a method of debugging in which the interested information is stored is much preferable because the timing is maintained. Some WMB facilities depend on timing. Getting in the habit of using Trace nodes for design and debugging which will save you a boat load of time trying to catch hard to find issues.

All these things in addition to what Vitor said, which was quite visionary.

Some basic rules for Trace nodes:

1. Put a trace node between each major node in your flow.

2. Make sure all terminals are attached to a unique Trace node.

3. Use Throw nodes if needed.

4. Don't put more than one input wire to any Trace node.

5. Make sure each unique Trace node writes to a unique file on disk.

6. Here is an example pattern:

Code:
Root:
${Root}
===
LocalEnvironment:
${LocalEnvironment}
===
Environment:
${Environment}
===
ExceptionList:
${ExceptionList}
===
${CURRENT_TIMESTAMP}
=======================


7. Get good at reading trace files.

8. If your trace files contain PCI or ePHI data, turn them off in Production through the mqsichangetrace command. Trace nodes that are off in Production consume virtually no resources.

_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
ipujals
PostPosted: Tue Feb 19, 2013 7:51 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

Finally, WMB developer informed me it's an WMB bug and I have made some workaround.

lancelotlinc, have you attended the required training for this product?
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 19, 2013 8:00 am    Post subject: Reply with quote

Grand High Poobah

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

ipujals wrote:
Finally, WMB developer informed me it's an WMB bug and I have made some workaround.


Does "WMB developer" in this context mean the developer you have writing the code, who has inserted additional ESQL or similar to avoid the problem, or does it mean the chap in Hursley who developed that part of WMB?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
adubya
PostPosted: Tue Feb 19, 2013 8:02 am    Post subject: Reply with quote

Partisan

Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK

What node type do you have connected to the collector Out terminal ?
Back to top
View user's profile Send private message Send e-mail
ipujals
PostPosted: Tue Feb 19, 2013 8:03 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

IBM WMB-software contact of our project.
Back to top
View user's profile Send private message
ipujals
PostPosted: Tue Feb 19, 2013 8:05 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

adubya wrote:
What node type do you have connected to the collector Out terminal ?


An ESQL compute node
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Feb 19, 2013 8:06 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

ipujals wrote:
IBM WMB-software contact of our project.


Is there an official APAR number?
Back to top
View user's profile Send private message
ipujals
PostPosted: Tue Feb 19, 2013 8:18 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jun 2012
Posts: 31

Hi mqjeff,

don't know, I only asked for the problem and they replied with the workaround. They only add SAP adapter have some problems (as said in this post) and there is no planning for now to fix them.

When I see them again, I'll ask and share with you.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Feb 19, 2013 8:24 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

ipujals wrote:
Finally, WMB developer informed me it's an WMB bug and I have made some workaround.

lancelotlinc, have you attended the required training for this product?


Yes, and have course completion certificates from IBM, along with the entire SOA product suite: WMQ, WPS, WESB, WAS, et al.

I wouldn't advocate something if I had not done it myself. The lecture was most interesting and helped me avoid many mistakes.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » XML Parsing error after Collection node
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.