| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Variable length final element |
« View previous topic :: View next topic » |
| Author |
Message
|
| Duncan |
 Posted: Mon Oct 21, 2002 11:14 pm Post subject: Variable length final element |
 |
|
Newbie
Joined: 11 Jul 2002
Posts: 3
|
I have what should be a simple message format:
Header (String, 25)
Unique ID (String, 24)
PDF(ADOBE) Document (Binary, End of Bitstream)
The message has been set up with a single type, ordered set, closed.
I get the following error in usertrace:
52276 UserTrace BIP2231E: Error detected whilst processing a message 'NLIS_PDF_FILE.Add Filename to PDF'.
The message broker detected an error whilst processing a message in node 'NLIS_PDF_FILE.Add Filename to PDF'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
52276 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'GEI'
Message Set Level : '1'
Message Format : 'CWF'
Message Type Path : 'NLIS_PDF_MESSAGE'
Review further error messages for an indication to the cause of the errors.
52276 ParserException BIP5171E: Custom Wire Format parsing error
An error occurred while parsing a Custom Wire Format message.
Current message : 'NLIS_PDF_MESSAGE'
Current element : 'NLIS_PDF_MESSAGE'
Path from message root : ''
Offset from start of message : 49
See following errors for more details.
52276 ParserException BIP5288E: MRM parsing error. Message bit stream larger than expected.
The bit stream of the message being parsed by the MRM parser is larger than expected for a message of this message type.
The message bit stream has been incorrectly constructed, or the logical model is incorrect.
Ensure that the message is correctly packaged.
Ensure that the message properties are correct.
Ensure that the logical model for this message type is complete (the message set and message type should be quoted in previous messages).
The length count is empty - as stated in Working with Messages. It deploys OK and fails as above when a message is sent through.
Has anyone got any suggestions? (Should I be using TDS instead of CWF?)
And if I get past this point, has anyone else tried sending an Adobe PDF through WMQI? Is it readable when it comes out the other end? |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Oct 23, 2002 9:06 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Do you just want to transport the PDF file thru MQ? Could you please explain what is the role of MQSI here?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Duncan |
| Posted: Wed Oct 23, 2002 10:47 pm Post subject: Adobe PDF in message |
|
|
Newbie
Joined: 11 Jul 2002
Posts: 3
|
The reason for using MQI is to allow routing of the file based on the Header information. The destination filename is built-up from the Unique ID as well.
I have used a BLOB format and SUBSTRING statements to get round this, but this requires manipulation in hex to create the filename so it's not ideal.
It seems to work this way, and the PDF can be opened and read even if the file name is still left concatenated at the beginning of the file.
I am still concerned that the original solution didn't work. Why can't the final element be read to end of bitstream if it's 'binary' (changing it to a 'string' element works fine, but the resulting file is obviously un-usable when reconstructed at the destination? |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Oct 24, 2002 7:54 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Duncan,
Thanks for the clarification. You don't have to use TDS for this. Your original solution should work if you have defined your 3rd (PDF data) field of Binary type into MRM and Length Units is set to "End Of Bitstream". Is it possible that your Message set is not deployed correctly to the broker. Try doing a complete deploy once again. If this does not solve your problem then try to turn on the Trace on your message flow.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| 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
|
|
|
|
