| Author |
Message
|
| rohank84 |
 Posted: Thu Jul 04, 2013 7:17 am Post subject: Error in the trace node |
 |
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
Hi Guys .... Broker version 8 with Mq 7.
I have a message flow which is throwing errors at the trace node. This si strange. I have Environment Tree in the trace node. The error occurs but the messages are written over the file and nothing seems to be wrong here ....The even viewer is full of error messages. Below are the errors. There message points at using a single property file ....probably this may be the issue but not sure. This code was working earlier but suddenly this has come up....
Error detected whilst processing a message in node 'PCI_AGR_HSBC_MSGFLW.PCI_AGR_HSBC_PAY_CO.PCI_AGR_HSBC_SUB.PCI_HSBC_LNK_SUB.Trace2'.
The message broker detected an error whilst processing a message in node 'PCI_AGR_HSBC_MSGFLW.PCI_AGR_HSBC_PAY_CO.PCI_AGR_HSBC_SUB.PCI_HSBC_LNK_SUB.Trace2'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
Either the message tree has a properties folder that is not the first element of the message tree, or it has two properties folders.
The Properties folder holds information about the characteristics of the message. If present, there must be only one properties folder and it must be the first element of the message tree, otherwise its fields will not have the desired effect.
Review the message flow and ESQL that caused this error and make sure that only one properties folder has been created, and that it is the first element of the message tree. By default, every occurrence of OutputRoot has a properties folder created automatically and a user should not create an additional one. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jul 04, 2013 7:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Sounds like you've put things in the Environment tree that are failing to serialize. |
|
| Back to top |
|
|
| rohank84 |
| Posted: Wed Jul 10, 2013 4:23 am Post subject: |
|
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
| so could this means there is a issue with the incoming message... |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jul 10, 2013 4:51 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| rohank84 wrote: |
| so could this means there is a issue with the incoming message... |
It more likely means that you've not correctly specified the pattern in the Trace node.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| rohank84 |
| Posted: Fri Jul 12, 2013 5:49 am Post subject: |
|
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
This is what I have in the trace node and looks fine...the file is also getting updated
${Environment}
-------------------------------------------------------------------- |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jul 12, 2013 5:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| rohank84 wrote: |
This is what I have in the trace node and looks fine...the file is also getting updated
${Environment}
-------------------------------------------------------------------- |
So what leads you to believe that the trace node is the root cause?
| rohank84 wrote: |
| I have a message flow which is throwing errors at the trace node. |
Can you post the error from the Broker logs?
What OS are you on? If on *nix, broker logs post to /var/adm/log.
What WMB version are you on? WMB versions have four digits.
What is your runtime's effective level?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 12, 2013 5:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It means the message tree you passed to the trace node is badly formed.
So when the trace node tries to serialize it, it fails.
Does the trace output show anything from the message at all?
I'd take a user trace of the flow, and see if you can tell what the flow is putting into the message tree before the trace node. |
|
| Back to top |
|
|
| rohank84 |
| Posted: Fri Jul 12, 2013 6:43 am Post subject: |
|
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
This what it prints in trace file
| Code: |
( ['MQROOT' : 0xd711c70]
(0x01000010:ParserRoot):XML = ( ['xml' : 0x9e76a90]
(0x01000000:Element):Variables = (
(0x01000000:Element):inMessageId = (
(0x02000000:pcdata): = '1-EBBMTD' (CHARACTER)
)
(0x01000000:Element):inMessageType = (
(0x02000000:pcdata): = 'Integration Object' (CHARACTER)
)
(0x01000000:Element):inIntObjectFormat = (
(0x02000000:pcdata): = 'Siebel Hierarchical' (CHARACTER)
)
(0x01000000:Element):inIntObjectName = (
(0x02000000:pcdata): = 'Quote - Credit Card - Solve SE - Authorise Payment Card - External' (CHARACTER)
)
(0x01000000:Element):RowId = (
(0x02000000:pcdata): = '1-16RZNOA' (CHARACTER)
)
(0x01000000:Element):NoOfInstalment = (
(0x02000000:pcdata): = '1' (CHARACTER)
)
(0x01000000:Element):SourceId = (
(0x02000000:pcdata): = 'CON1' (CHARACTER)
)
(0x01000000:Element):OriginalUnroundedAmount = (
(0x02000000:pcdata): = '61.59' (CHARACTER)
)
(0x01000000:Element):CardNumber = (
(0x02000000:pcdata): = '67673673672632' (CHARACTER)
)
(0x01000000:Name ):Properties = ( ['MQPROPERTYPARSER' : 0xd99c390]
(0x03000000:NameValue):MessageSet = '' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Transactional = TRUE (BOOLEAN)
(0x03000000:NameValue):Persistence = FALSE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2013-07-12 13:51:22.940' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'414d5120514d5f53424c5f5052445f3251adc5292028f30f' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name ):MQMD = ( ['MQHMD' : 0xd9bd110]
(0x03000000:NameValue):SourceQueue = 'M_SBL_HSBC_CRD_INPT' (CHARACTER)
(0x03000000:NameValue):Transactional = TRUE (BOOLEAN)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Format = 'MQSTR ' (CHARACTER)
(0x03000000:NameValue):Version = 2 (INTEGER)
(0x03000000:NameValue):Report = 56623107 (INTEGER)
(0x03000000:NameValue):MsgType = 8 (INTEGER)
(0x03000000:NameValue):Expiry = -1 (INTEGER)
(0x03000000:NameValue):Feedback = 0 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):Persistence = 0 (INTEGER)
(0x03000000:NameValue):MsgId = X'414d5120514d5f53424c5f5052445f3251adc5292028f30f' (BLOB)
(0x03000000:NameValue):CorrelId = X'414d5120514d5f53424c5f5052445f3251adc5292028f30f' (BLOB)
(0x03000000:NameValue):BackoutCount = 0 (INTEGER)
(0x03000000:NameValue):ReplyToQ = 'R_SOLVESE_QUOTE_AUTHPAY ' (CHARACTER)
(0x03000000:NameValue):ReplyToQMgr = 'QM_SBL_PRD_21 ' (CHARACTER)
(0x03000000:NameValue):UserIdentifier = 'sadmin ' (CHARACTER)
(0x03000000:NameValue):AccountingToken = X'0432303137000000000000000000000000000000000000000000000000000006' (BLOB)
(0x03000000:NameValue):ApplIdentityData = ' ' (CHARACTER)
(0x03000000:NameValue):PutApplType = 6 (INTEGER)
(0x03000000:NameValue):PutApplName = ' ' (CHARACTER)
(0x03000000:NameValue):PutDate = DATE '2013-07-12' (DATE)
(0x03000000:NameValue):PutTime = GMTTIME '13:51:22.940' (GMTTIME)
(0x03000000:NameValue):ApplOriginData = ' ' (CHARACTER)
(0x03000000:NameValue):GroupId = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
(0x03000000:NameValue):Offset = 0 (INTEGER)
(0x03000000:NameValue):MsgFlags = 0 (INTEGER)
(0x03000000:NameValue):OriginalLength = -1 (INTEGER)
)
)
)
) |
|
|
| Back to top |
|
|
| rohank84 |
| Posted: Fri Jul 12, 2013 6:46 am Post subject: |
|
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
The broker version is 8.0.0.1
Windows Server 2008 R2 Enterprise
I have pasted the message logged in the environment tree ....does it seem ok ? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jul 12, 2013 6:59 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 12, 2013 9:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rohank84 wrote: |
This what it prints in trace file
[code]
( ['MQROOT' : 0xd711c70]
(0x01000010:ParserRoot):XML = ( ['xml' : 0x9e76a90] |
Don't use XML parser, use XMLNSC.
Also, this is the first child of Root, not the last child. This is your problem. |
|
| Back to top |
|
|
| rohank84 |
| Posted: Wed Jul 17, 2013 1:40 am Post subject: |
|
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
This is coming in production env so cant run a user trace on it. The errors are logged in Windows Event Viewer...is there any place else i can check the logs....
We are upgrading it to 8002 but that not going to happen for another month.
Is there any other possiblities ...
Thanks for helping me so far. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jul 17, 2013 2:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The problem is that the flow is building the message tree in the wrong order.
It has put the XML data as the first child of the message tree, rather than the last child.
You can't change the Trace node to work properly with that. You can't change the MQOutput node or any other output node to work properly with that.
You have to change the flow to build the tree in the right order. |
|
| Back to top |
|
|
| rohank84 |
| Posted: Mon Jul 29, 2013 1:14 am Post subject: |
|
|
Centurion
Joined: 31 Dec 2008
Posts: 109
|
Hi Guys....
The message flow was developed in broker v6.0 and was deployed without any midification to v8......
This may be causing the issue. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jul 29, 2013 3:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| The message flow was developed in broker v6.0 and was deployed without any midification to v8 |
It would have been helpful to explain that in your first post...
| Quote: |
| This may be causing the issue |
Possibly. There is no supported migration path from v6.0 to v8.0.0.x. mqjeff's advice is good advice - take a user trace, and look at how the message tree is being built.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
|
|
