| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message set parsing issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| Jenney |
 Posted: Fri Feb 29, 2008 8:46 am Post subject: Message set parsing issue |
 |
|
Voyager
Joined: 25 Apr 2007
Posts: 83
Location: Melbourne
|
Hi,
We have Brk V6, on win. I have created a message set for CWF input message which Brk is suppose to convert to XML.
I have some repeating elements as stated below, and this Information element repeats 4 times all together.
Information Min Occ = 4, Max occur=4
FactorLine Min Occ = 4, Max occur=4
FactorLine1 Min Occ = 1, Max occur=1
FactorLine2 Min Occ = 1, Max occur=1
FactorLine3 Min Occ = 1, Max occur=1
SFactor Min Occ = 4, Max occur=4
| Quote: |
Information
FactorLine
FactorLine1 = TESTFactorLine1
FactorLine2 = TESTFactorLine2
FactorLine3 = TESTFactorLine3
FactorLine
FactorLine1 = TESTFactorLine1
FactorLine2 = TESTFactorLine2
FactorLine3 = TESTFactorLine3
FactorLine
FactorLine1 = TESTFactorLine1
FactorLine2 = TESTFactorLine2
FactorLine3 = TESTFactorLine3
FactorLine
FactorLine1 = TESTFactorLine1
FactorLine2 = TESTFactorLine2
FactorLine3 = TESTFactorLine3
SFactor=
SFactor=
SFactor=
SFactor=
|
Broker gives error while processing the FactorLine2 in the last itteration of Information (4th itteration)>FactorLine (4th itteration). Which i don't understand how to resolve, Incomming message looks good to me.
This message worked 15 days ealier and now i am seeing this error. I recreated the message set but still it fails at the same point.
| Quote: |
| CWFWorker::ReadDataFromBitstream - CPI Text Buffer Input Data Too Short |
Any idea what's happening, any inputs will be a great help.
thanks
Jen |
|
| Back to top |
|
 |
| kimbert |
| Posted: Sun Mar 02, 2008 3:27 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You could temporarily extend the input message by a few characters until you get a successful parse. Then look at the resulting message tree ( debugger or Trace node ) and see what went wrong.
If other messages in the same format are parsing OK, check for code page issues (e.g. multi-byte characters ) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 02, 2008 5:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| kimbert wrote: |
You could temporarily extend the input message by a few characters until you get a successful parse. Then look at the resulting message tree ( debugger or Trace node ) and see what went wrong.
If other messages in the same format are parsing OK, check for code page issues (e.g. multi-byte characters ) |
Check as well for ftp issues on messages built from a file.
If ftp'd in binary form for a text content you might get this message or it's opposite (stream too short/not all data on stream needed). It has to do with the carriage line feed not being the same length depending on the environment (1 byte vs 2 bytes)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
