| Author |
Message
|
| gorjy |
 Posted: Tue Jul 26, 2005 5:13 am Post subject: A wierd problem |
 |
|
Novice
Joined: 15 Jul 2005
Posts: 18
Location: Bulgaria, Sofia
|
Believe it or not, but the set of MessageFlows and MessageSets, that works just fine on a production server, after being transfered to a test server, just doesn't work - it fails.
At a certain point, which I know - a simple filter, which checks if the input message contains if a string like this '311', the system generates the following message error:
Error detected whilst executing the SQL statement XXX. Message Translation Interface Parsing Errors have occurred. MRM parsing error. Message bit stream larger than expected.
Excuse me for the question, but can anyone tell me what does this message mean? |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Tue Jul 26, 2005 5:41 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
|
| Back to top |
|
|
| gorjy |
| Posted: Tue Jul 26, 2005 5:53 am Post subject: Re: |
|
|
Novice
Joined: 15 Jul 2005
Posts: 18
Location: Bulgaria, Sofia
|
Thanks, but I have checked already the mentioned PDF file.
It says that if you upgrade from CSD02 to CSD03 or higher could arise such a problem, but doesn't help me, because I have installed firstly the Broker version 5 and then applied the patch CSD09.
Any other suggestions. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 26, 2005 6:19 am Post subject: Re: A wierd problem |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| gorjy wrote: |
Message bit stream larger than expected.
Excuse me for the question, but can anyone tell me what does this message mean? |
That means that the data was larger than the message set instructed Broker to think it was.
So it's a problem with the message set or the message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fschofer |
| Posted: Tue Jul 26, 2005 6:25 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
the message flow starts parsing your data with the defined message set the first time you try to acccess it with you filter node.
| Quote: |
| Message bit stream larger than expected |
means that one or some of the fields in your message is to long.
This could for example be a problem with <CR><LF> <=> <LF>.
Are your production and test system running on th same platform ?
Greetings
Frank |
|
| Back to top |
|
|
| gorjy |
| Posted: Tue Jul 26, 2005 6:33 am Post subject: Re: |
|
|
Novice
Joined: 15 Jul 2005
Posts: 18
Location: Bulgaria, Sofia
|
The real problem is that it works just fine on the production server and I have to fix just a part of it, not rewrite it.
jefflowrey: I can't find out why it works on one machine and not on another.
Frank: The 'production' runs on Windows 2000 (not sure about SPs), but works with the UNIX character set table. The 'test' is on a normal Windows 2003 w SP1.
On the production server the MessageSets' elements are defined to be tag delimited and be '0' in length. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 26, 2005 6:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A trace that includes Root should show you the last element it was able to successfully parse. That will tell you approximately where the problem is.
Again, the problem is either with your message set or with the message itself. You say the set works in production - can it parse the same message that fails in test?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| scottm |
| Posted: Tue Jul 26, 2005 7:15 am Post subject: |
|
|
Apprentice
Joined: 13 May 2004
Posts: 44
Location: SE Tennessee
|
We get that message all the time.
And it's always (in our case) because the message coming in has an element that is larger that what the message set is expecting (defined for). The error was in the message, not the message set or the message flow.
Does the exact message succeed in production and fail in test? Or are they different messages?
Is the validation setting different on test as compared to production? |
|
| Back to top |
|
|
| gorjy |
| Posted: Wed Jul 27, 2005 1:47 am Post subject: Re: |
|
|
Novice
Joined: 15 Jul 2005
Posts: 18
Location: Bulgaria, Sofia
|
| scottm wrote: |
| Or are they different messages? |
No, they are the same. To be precise the messages I am testing with are downloaded from the production server(not by me), by saving them into a file and transfering the file to the test machine. I am think of diverting the PROD server incoming messages to a TEST server queue.
After inserting trace files - before and after a particular point (Reset Content Descriptor), I think a MRM parser is not parsing correctly the income message, because after the 'RCD' the message body is empty. In the trace file is written just the parsed message type.
Not having figuring out what is the real problem, I have a question:
Does it matter what program is used to put the messages?
I am using one called: WMQ Tool 5.3 , written in Java, from the company niratul.
Can you advise me anything, since the PROD and TEST Flows' and Sets' settings are the same? |
|
| Back to top |
|
|
| gorjy |
| Posted: Wed Jul 27, 2005 6:53 am Post subject: RE: the PROBLEM is OVER |
|
|
Novice
Joined: 15 Jul 2005
Posts: 18
Location: Bulgaria, Sofia
|
Thanks to all who gave suggestions.
Apperantly somehow I have mixed up the messageSets' IDs while saving the projects and deploying them.
Thanks. |
|
| Back to top |
|
|
|
|
