| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MRM Parsing Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| jai1234 |
 Posted: Fri Jan 07, 2005 4:53 am Post subject: MRM Parsing Error |
 |
|
Novice
Joined: 02 Dec 2004
Posts: 10
|
Hi
I am getting the following error in the Event Viewer when the message flow is tring to parse an MRM message set with wire format CwXML:
( WMQI_BROKER.VehicleJDBC ) 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).
( WMQI_BROKER.VehicleJDBC ) Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'tst_VEHICLES'
Message Set Level : '1'
Message Format : 'CwXML'
Message Type Path : 'tst_VEHICLES'
Review further error messages for an indication to the cause of the errors.
I read from one of the postings found by a search in google that this issue has been fixed and rolled out in CSD04. I am using WMQI2.1 + CSD04.
Can anyone help me out?
Regards,
Jai |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jan 07, 2005 6:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You have a message that gets picked up by broker.
That message is, for example, 100 bytes long.
The message model that is assigned to parse this message only describes, for example, 90 bytes.
Then this error is thrown.
It is a problem in your model, or a problem in your data.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Fri Jan 07, 2005 11:26 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Check that didn't miscalculate the length of a field. One of the common ones is to forget formatting characters like the ":" in 3:00 or the "," in 1,000. This can be especially maddening if you are working with human input data from a terminal or website.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| kirani |
| Posted: Sat Jan 08, 2005 4:27 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Also, please provides details on your input layout. It seems like your input is in CWF format? Do you have a copybook layout?
If you are using COBOL Record format to model your input message then it gets tricky when you deal with Binary fields, for example, COMP-3 etc.
_________________
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 |
|
|
| jai1234 |
| Posted: Mon Jan 10, 2005 3:28 am Post subject: MRM Parsing Error |
|
|
Novice
Joined: 02 Dec 2004
Posts: 10
|
Hi
I am not using COBOL copybooks. I am trying a WBI Adapter (JDBC Adapter) to get it work with WMQI 2.1 broker. The message set is been created using a batch file provided when a business object definition is created using BO Designer tool. Basically the connector would be using the message set definition which matches the business object definition. The wire format been used by the adapter/connector is CwXML which is XML Wire format layer. The transport protocol been used is WMQI-JMS. Since a message set is been used, in the input node of my message flow I have specified the following :
Message Domain : MRM
Message Set : (the message set id generated by the batch file)
Message Type : EMP (the table definition being used is EMP from which a BO definition has been acquired. The BO definition maps to a message set)
Message Format : CwXML
Trace File Dump (trace node attached after the input node)
(0x1000000)Properties = (
(0x3000000)MessageSet = 'E3A2VHK096001'
(0x3000000)MessageType = 'EMP'
(0x3000000)MessageFormat = 'CwXML'
(0x3000000)Encoding = 273
(0x3000000)CodedCharSetId = 1208
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = TRUE
(0x3000000)CreationTime = GMTTIMESTAMP '2005-01-10 10:48:27.030'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 4
(0x3000000)ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x3000000)ReplyProtocol = 'MQ'
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'VehicleJDBCConnector/DELIVERYQUEUE'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 273
(0x3000000)CodedCharSetId = 819
(0x3000000)Format = 'MQHRF2 '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 4
(0x3000000)Persistence = 1
(0x3000000)MsgId = X'414d512042726f6b65725f514d202020900ee24120002002'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'Broker_QM '
(0x3000000)UserIdentifier = 'jai '
(0x3000000)AccountingToken = X'16010515000000be043e32833d2b4607e53b2be803000000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = '\Softwares\WBIA\bin\java.exe'
(0x3000000)PutDate = DATE '2005-01-10'
(0x3000000)PutTime = GMTTIME '10:48:27.030'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000000)MQRFH2 = (
(0x3000000)Version = 2
(0x3000000)Format = 'MQSTR '
(0x3000000)Encoding = 273
(0x3000000)CodedCharSetId = 1208
(0x3000000)Flags = 0
(0x3000000)NameValueCCSID = 1208
(0x1000000)mcd = (
(0x1000000)Msd = (
(0x2000000) = 'mrm'
)
(0x1000000)Set = (
(0x2000000) = 'E3A2VHK096001'
)
(0x1000000)Type = (
(0x2000000) = 'EMP'
)
(0x1000000)Fmt = (
(0x2000000) = 'CwXML'
)
)
(0x1000000)jms = (
(0x1000000)Dst = (
(0x2000000) = 'queue:///VehicleJDBCConnector/DELIVERYQUEUE'
)
(0x1000000)Tms = (
(0x2000000) = '1105354107031'
)
(0x1000000)Dlv = (
(0x2000000) = '2'
)
)
)
(0x1000021)MRM = (
XML Message Dump
<?xml version="1.0" encoding="UTF-8"?>
<EMP:EMP xmlns:EMP="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/EMP"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/EMP file:EMP.xsd" version="1.0.0" delta="false" verb="Create" locale="en_US">
<EMP:EMPID>4</EMP:EMPID>
<EMP:ObjectEventId>JDBCConnector_1105354106890_2</EMP:ObjectEventId>
</EMP:EMP>
Business Object Definition
<StartHeader>
<Version = 3.0>
<EndHeader>
<StartBO:EMP>
BusinessObject = EMP
Verb = Create
Locale = en_US
EMPID = 4
ObjectEventId = JDBCConnector_1105354106890_2
<EndBO:EMP>]
JMS Header Dump
JMS Message class: jms_text
JMSType: mcd://mrm/E3A2VHK096001/EMP?format=CwXML
JMSDeliveryMode: 2
JMSExpiration: 0
JMSPriority: 4
JMSMessageID: ID:414d512042726f6b65725f514d202020900ee24120002002
JMSTimestamp: 1105354107031
JMSCorrelationID:null
JMSDestination: queue:///VehicleJDBCConnector/DELIVERYQUEUE
JMSReplyTo: null
JMSRedelivered: false
JMS_IBM_PutDate:20050110
JMSXAppID:\Softwares\WBIA\bin\java.exe
JMS_IBM_PutApplType:11
JMSXUserID:jai
JMS_IBM_PutTime:10482703
JMSXDeliveryCount:0
I have absolutely have no clue on what is going wrong. The field name EmpId in the message set EMP can hold upto 4 characters in length. If I key in 5 or 6 characters as input, then I get an error in the Event Viewer saying "Overflow of characters" which is quite logical. If I key in less than 4 characters, then I get the error message "MRM parsing error. Message bit stream larger than expected."
---
Jai |
|
| 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
|
|
|
|
