| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP5285E BIP5180E |
« View previous topic :: View next topic » |
| Author |
Message
|
| Herbert |
 Posted: Wed Jan 05, 2011 3:10 am Post subject: BIP5285E BIP5180E |
 |
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
Hi,
I get below errors with a WMB flow, it looks very simple, WMB tells me that the combination Message set/type/format does not exist during runtime in the execution group.
I really think that is not true, did check it many times, its there ....
I can select those settings with pulldown in the toolkit (I did not type it myself). MRM is activated for the message set and the .dictionary file is deployed in the execution group.
The message properties are activated with a ResetContentDescriptor inside a subflow with promoted properties for the 4 message properties (domain/set/type/format)
I did a lot troubleshoot things, checking many times, redepoyment after emptying the execution group, workspace rebuild, etc. not working at all.
What I'm I missing here ?
Herbert
| Code: |
BIP5285E: Parsing errors have occurred. Message set name: 'IBA_CustomerAccounts' Message forma
t: 'CBL' Message type path: '/msg_CUSTOMERACCOUNTS (default namespace)'
Review other error messages to find the cause of the errors.
----------[2011-01-05 11:02:10.490697 7291 ParserException ]---------------------------------
BIP5180E: A Custom Wire Format error has occurred. An unknown message type has been identified for m
essage set ''OS265T0002001''
The Custom Wire Format parser or writer has received an unknown message type identifier in
the message properties.
The specified message set (''OS265T0002001'') does not contain a message type with this id
entifier.
Previous errors will supply the message set name and the message type identifier.
Check that the supplied message identifier is correct.
Check that the supplied message set identifier is correct.
Check that the message set contains a message type with the specified identifier.
|
|
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jan 05, 2011 12:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Wouldn't the message format be something like 'CWF' or 'CWF1' instead of
| Quote: |
BIP5285E: Parsing errors have occurred. Message set name: 'IBA_CustomerAccounts' Message format: 'CBL' Message type path: '/msg_CUSTOMERACCOUNTS (default namespace)'
|
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jan 05, 2011 3:21 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Wouldn't the message format be something like 'CWF' or 'CWF1' |
Those are just the defaults ( pre-v5.0 and post-v5.0 respectively ). You can choose any name you like for an MRM physical format.
| Quote: |
| WMB tells me that the combination Message set/type/format does not exist |
It is claiming that message type '/msg_CUSTOMERACCOUNTS' does not exist in message set 'OS265T0002001'. I would check the following, in this order:
1. check that the message set id is the one that you expected the flow to be using.
2. check that this message set contains a global element with name 'msg_CUSTOMERACCOUNTS' ( a global complex type will not do )
3. if 1. and 2. look OK, see whether removing the leading forward-slash makes things better ( this is a long shot )
If those steps don't reveal the problem, I suggest that you take a user trace of the attempted parse and read it carefully to see what actual values the flow is using for set/type/format. |
|
| Back to top |
|
|
| Herbert |
| Posted: Thu Jan 06, 2011 5:19 am Post subject: |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
I did indeed manually rename the format to CBL.
It was a message set with a lot of refactoring history. The end result was simple, just 4 cobol copy books with no manual changes needed.
I created the message set again from scratch from those 4 copy books and it did work again. Ok, the flow was not working  But the errors that then did popup where correct, eq:
BIP5288E: An MRM parsing error has occurred. The bit stream of the message being parsed by the MRM parser is larger than expected for a message of this type. Number of bytes parsed: 15 Actual length of message: 1429
IMHO the broker did give incorrect the BIP5180E (unknown message type) error where it should have given the BIP5288E (larger than expected) error.
Btw: the BIP5285E in front of those 2 errors is the same in both situations, including / for the Message type. The / is not visuable in the toolkit when selecting the Message Type as property, but its there in the trace output.
Thanks for the feedback and thoughts. |
|
| 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
|
|
|
|
