| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Repeating structure in a CWF message set |
« View previous topic :: View next topic » |
| Author |
Message
|
| prk |
 Posted: Mon Mar 17, 2008 12:01 pm Post subject: Repeating structure in a CWF message set |
 |
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Hi,
We are using MQ 6.0.2 and Message Broker 6.0.3. I have a msg coming from SAP with repeating segments and I have an MRM (CWF) going out. The whole MRM structure needs to repeat "n" number of times for the "n" number of times the segment repeats in SAP. I found a way of creating a complex element and specifying the repeat reference but thats too complicated. Want to see if anyone has any better ideas. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Mar 18, 2008 5:32 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| You're using v6. You should be able to build a message tree containing as many occurrences as you need. The only restriction is that the repeating structure must be the final structure in the model/bitstream. |
|
| Back to top |
|
|
| prk |
| Posted: Tue Mar 18, 2008 7:19 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Kimbert,
Thanks for the response. Yes, my repeating structure is at the end of the bitstream but how can I do it. Could you please provide some details. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Mar 18, 2008 7:28 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
1. In the message definition file, set maxOccurs on the element to -1
2. In the message flow, build the message tree with as many occurrences as you like
It should just work. If it doesn't, please give full details of what you tried, with the full text of all error messages. |
|
| Back to top |
|
|
| prk |
| Posted: Tue Mar 18, 2008 8:00 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
I have 3 segments coming from SAP. Control rec, y segment and i segment. The i segment is a repeater. I have a message set with 3 fields for control record set to 1,1 (min occurs and max occurs) and 5 fields for y segment set to 1,1 (min occurs and max occurs) and 10 fields for the I segment set to 1, -1 (min occurs and max occurs) since its a repeater.
It parses the tree fine but when it writes the msg to the output queue, I get this error in the system log and msg ends up in the failure queue.
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP2232E: Error detected whilst handling a previous error in node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw'. : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/DataFlowEngine/ImbDataFlowNode.cpp: 430: ImbDataFlowNode::logExceptionList: ComIbmThrowNode: SAP_FDG_WMMBID02_ADAPTER#FCMComposite_1_19.SF_ERROR_HANDLER_ADAPTER#FCMComposite_1_3
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP2230E: Error detected whilst processing a message in node 'SAP_FDG_WMMBID02_ADAPTER.MQSI.QL.TD.WMMBID02'. : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/DataFlowEngine/ImbMqOutputNode.cpp: 782: ImbMqOutputNode::evaluate: ComIbmMQOutputNode: SAP_FDG_WMMBID02_ADAPTER#FCMComposite_1_2
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP5286E: Message Translation Interface Writing Errors have occurred: Message Set Name : 'FDG_WMMBID02' Message Set Level : '1' Message Format : 'CWF' Message Type Path : 'FDG_WMMBID02' : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/MTI/MTIforBroker/MtiImbParser2/MtiImbParser.cpp: 1711: MtiImbParser::refreshBitStreamFromElements - 9 par: ComIbmComputeNode: SAP_FDG_WMMBID02_ADAPTER#FCMComposite_1_4
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP5167E: Custom Wire Format error while parsing/writing message 'FDG_WMMBID02'. : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/cpi/pwf/cwf/cwfworker.cpp: 415: CWFWorker::write: :
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP5350E: Custom Wire Format writing error. While writing the message quoted above, the CWF writer encountered an error. The error occurred during or after the writing of element '/FDG_WMMBID02/WERKS'. : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/cpi/pwf/cwf/cwfmessage.cpp: 618: CMessage::write: :
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP5344E: CWF Output: Mismatch between logical definition and message tree. Message : FDG_WMMBID02 Element : 65^MATNR : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/cpi/pwf/cwf/cwfcontext.cpp: 323: CContext::CheckDefaultValue: :
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP2628E: Exception condition detected on input node 'SAP_FDG_WMMBID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02'. : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_EP/src/DataFlowEngine/ImbCommonInputNode.cpp: 1099: ImbCommonInputNode::run: ComIbmMQInputNode: SAP_FDG_WMMBID02_ADAPTER#FCMComposite_1_1
Mar 18 11:55:51 prh354 WebSphere Broker v6003[22047]: (PRH354BKRD.EG_SAP_FDG)[31]BIP3001I: Exception thrown by throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw'; text is ''. : PRH354BKRD.d5862aa4-1801-0000-0080-d5e1dfe45795: /build/S600_P/src/DataFlowEngine/BasicNodes/ImbThrowNode.cpp: 265: ImbThrowNode::evaluate: ComIbmThrowNode: SAP_FDG_WMMBID02_ADAPTER#FCMComposite_1_19.SF_ERROR_HANDLER_ADAPTER#FCMComposite_1_3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 18, 2008 8:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kimbert wrote: |
| the full text of all error messages. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prk |
| Posted: Tue Mar 18, 2008 8:59 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
I have attached the full text from the system log before and here is the error message from the user trace.
2008-03-18 11:32:56.498028 31 UserTrace BIP4241I: Message propagated to target Label node by RouteToLabel node 'SAP
_FDG_WMMBID02_ADAPTER.RouteToLabel'.
A RouteToLabel node has received a message and is propagating it to the appropriate La
bel node.
No user action required.
2008-03-18 11:32:56.498116 31 UserTrace BIP4220I: Message propagated to out terminal from node 'SAP_FDG_WMMBID02_AD
APTER.Germany'.
A label node has received a message and is propagating it to any nodes connected to it
s out terminal.
No user action required.
2008-03-18 11:32:56.552548 31 UserTrace BIP2231E: Error detected whilst processing a message in node 'SAP_FDG_WMMBI
D02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02'.
The message broker detected an error whilst processing a message in node 'SAP_FDG_WMMB
ID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02'. 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.
2008-03-18 11:32:56.552664 31 RecoverableException BIP2230E: Error detected whilst processing a message in node 'SAP
_FDG_WMMBID02_ADAPTER.MQSI.QL.TD.WMMBID02'.
The message broker detected an error whilst processing a message in node 'SAP_FDG_WMMB
ID02_ADAPTER.MQSI.QL.TD.WMMBID02'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-03-18 11:32:56.552700 31 ParserException BIP5286E: Message Translation Interface Writing Errors have occurred:
Message Set Name : ''FDG_WMMBID02'' Message Set Level : '1' Message Format : ''CWF'' Message Type Path : ''FDG_WMMBID
02''
Review further error messages for an indication to the cause of the errors.
2008-03-18 11:32:56.552724 31 ParserException BIP5167E: Custom Wire Format error while parsing/writing message ''FDG
_WMMBID02''.
2008-03-18 11:32:56.552748 31 ParserException BIP5350E: Custom Wire Format writing error. While writing the message
quoted above, the CWF writer encountered an error. The error occurred during or after the writing of element ''/FDG_WMMBID02
/WERKS''.
Check that you have built the message correctly.
See following messages for more details.
2008-03-18 11:32:56.552772 31 ParserException BIP5344E: CWF Output: Mismatch between logical definition and message
tree. Message : 'FDG_WMMBID02' Element : '65^MATNR'
The CWF writer has been given a message tree which does not match the logical message
definition.
The elements may have been added to the message tree in the wrong order, or there may
be elements missing from the message tree.
The message type or message set may be incorrect.
If the output message was assembled in a Compute node, check that the elements were ad
ded to the message in the order specified in the logical message definition.
Check that the output message contains all the elements in the logical message definit
ion (perhaps you need to copy the entire input message to the output tree before modifying it)
Check that the output message has the correct message set and message type properties.
Check that the output message does not contain self-defining elements.
Check that any missing elements have default values defined.
2008-03-18 11:32:56.553780 31 UserTrace BIP2540I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace': F
inished evaluating expression ''CURRENT_TIMESTAMP'' at ('', '2.9'). The result was ''TIMESTAMP '2008-03-18 11:32:56.552848'''
.
2008-03-18 11:32:56.555332 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace': E
valuating expression ''Root'' at ('', '4.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 N
ameSpace='' Name='Root' Value=NULL''.
2008-03-18 11:32:56.634736 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace': E
valuating expression ''ExceptionList'' at ('', '5.3'). This resolved to ''ExceptionList''. The result was ''ROW... Root Eleme
nt Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2008-03-18 11:32:56.650996 31 UserTrace BIP4067I: Message propagated to output terminal for trace node 'SAP_FDG_WMM
BID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace'.
The trace node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace' has received
a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2008-03-18 11:32:56.651164 31 UserTrace BIP4101I: Exception thrown by throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR
_HANDLER_ADAPTER.Throw'.
The throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw' has received
a message and will throw an exception as this is its normal behavior.
No user action required.
2008-03-18 11:32:56.662380 31 Error BIP2232E: Error detected whilst handling a previous error in node 'SAP_FDG_
WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw'.
The message broker has detected an error in node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HA
NDLER_ADAPTER.Throw' whilst handling a previous error.
See the following messages for details of the exception list associated with the origi
nal error. Thereafter messages will be associated with the new error.
2008-03-18 11:32:56.662468 31 RecoverableException BIP2230E: Error detected whilst processing a message in node 'SAP
_FDG_WMMBID02_ADAPTER.MQSI.QL.TD.WMMBID02'.
The message broker detected an error whilst processing a message in node 'SAP_FDG_WMMB
ID02_ADAPTER.MQSI.QL.TD.WMMBID02'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-03-18 11:32:56.662500 31 ParserException BIP5286E: Message Translation Interface Writing Errors have occurred:
Message Set Name : ''FDG_WMMBID02'' Message Set Level : ''1'' Message Format : ''CWF'' Message Type Path : ''FDG_WMMB
ID02''
Review further error messages for an indication to the cause of the errors.
2008-03-18 11:32:56.662520 31 ParserException BIP5167E: Custom Wire Format error while parsing/writing message ''FDG
_WMMBID02''.
2008-03-18 11:32:56.662544 31 ParserException BIP5350E: Custom Wire Format writing error. While writing the message
quoted above, the CWF writer encountered an error. The error occurred during or after the writing of element ''/FDG_WMMBID02
/WERKS''.
Check that you have built the message correctly.
See following messages for more details.
2008-03-18 11:32:56.662568 31 ParserException BIP5344E: CWF Output: Mismatch between logical definition and message
tree. Message : 'FDG_WMMBID02' Element : '65^MATNR'
The CWF writer has been given a message tree which does not match the logical message
definition.
The elements may have been added to the message tree in the wrong order, or there may
be elements missing from the message tree.
The message type or message set may be incorrect.
If the output message was assembled in a Compute node, check that the elements were ad
ded to the message in the order specified in the logical message definition.
Check that the output message contains all the elements in the logical message definit
ion (perhaps you need to copy the entire input message to the output tree before modifying it)
Check that the output message has the correct message set and message type properties.
Check that the output message does not contain self-defining elements.
Check that any missing elements have default values defined.
2008-03-18 11:32:56.667420 31 Error BIP2628E: Exception condition detected on input node 'SAP_FDG_WMMBID02_ADAP
TER.MQSI.QL.ADAPTER.WMMBID02'.
The input node 'SAP_FDG_WMMBID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02' detected an error w
hilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work,
it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, an
d take action as described by those messages.
2008-03-18 11:32:56.667480 31 UserException BIP3001I: Exception thrown by throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ER
ROR_HANDLER_ADAPTER.Throw'; text is ''''.
The throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw' has received
a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception i
s ''''.
Since this is application generated (by message flow behavior), the user action is det
ermined by the message flow and the type of exception generated.
2008-03-18 11:32:57.685972 31 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'SA
P_FDG_WMMBID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02'.
Node 'SAP_FDG_WMMBID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02' has received a message which
has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exc
eeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the mess
age to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being
backed out. Correct this situation if possible. Perform any local error recovery processing required.
2008-03-18 11:32:57.687384 31 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'SAP_FDG_WMM
BID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2008-03-18 11:32:57.687624 31 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'SAP_FDG_WMMBID02_
ADAPTER.MQSI.QL.ADAPTER.WMMBID02' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser
type selected based on value ''MQHMD'' from previous parser.
2008-03-18 11:32:57.688148 31 UserTrace BIP6061I: Parser type ''XML'' created on behalf of node 'SAP_FDG_WMMBID02_A
DAPTER.MQSI.QL.ADAPTER.WMMBID02' to handle portion of incoming message of length '14563' bytes beginning at offset '364'. Par
ser type selected based on value ''XML'' from previous parser.
2008-03-18 11:32:57.690472 31 UserTrace BIP2537I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
xecuting statement ''BEGIN ... END;'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '1.40').
2008-03-18 11:32:57.690836 31 UserTrace BIP2537I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
xecuting statement ''SET OutputRoot = InputRoot;'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '2.2').
2008-03-18 11:32:57.691216 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''InputRoot'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '2.19'). This resolved to ''InputRoot''. The r
esult was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2008-03-18 11:32:57.691376 31 UserTrace BIP2568I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': C
opying sub-tree from ''InputRoot'' to ''OutputRoot''.
2008-03-18 11:32:57.693004 31 UserTrace BIP2537I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
xecuting statement ''IF InputRoot.MQRFH.CodedCharSetId = 0 AND InputRoot.MQMD.CodedCharSetId <> 500 THEN... END IF;'' at ('
.SF_FAILURE_ADAPTER_Fix Headers.main', '5.2').
2008-03-18 11:32:57.695044 31 UserTrace BIP2543I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': (
'.SF_FAILURE_ADAPTER_Fix Headers.main', '5.5') : Failed to navigate to path element number '2' because it does not exist.
2008-03-18 11:32:57.695296 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''InputRoot.MQRFH.CodedCharSetId'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '5.5'). This resolved to
''InputRoot.MQRFH.CodedCharSetId''. The result was ''EMPTY ROW''.
2008-03-18 11:32:57.695528 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''InputRoot.MQRFH.CodedCharSetId = 0'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '5.36'). This resolve
d to ''EMPTY ROW = 0''. The result was ''NULL''.
2008-03-18 11:32:57.695940 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''InputRoot.MQMD.CodedCharSetId'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '6.3'). This resolved to '
'InputRoot.MQMD.CodedCharSetId''. The result was ''ROW... Root Element Type=50331648 NameSpace='' Name='CodedCharSetId' Value
=819''.
2008-03-18 11:32:57.696200 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''InputRoot.MQMD.CodedCharSetId <> 500'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '6.33'). This resol
ved to ''ROW... Root Element Type=50331648 NameSpace='' Name='CodedCharSetId' Value=819 <> 500''. The result was ''TRUE''.
2008-03-18 11:32:57.696376 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''InputRoot.MQRFH.CodedCharSetId = 0 AND InputRoot.MQMD.CodedCharSetId <> 500'' at ('.SF_FAILURE_ADAPTER
_Fix Headers.main', '5.40'). This resolved to ''NULL AND TRUE''. The result was ''NULL''.
2008-03-18 11:32:57.696516 31 UserTrace BIP2537I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
xecuting statement ''IF OutputRoot.MQMD.Format = ' ' THEN... END IF;'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '
11.2').
2008-03-18 11:32:57.696852 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''OutputRoot.MQMD.Format'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '11.5'). This resolved to ''Outpu
tRoot.MQMD.Format''. The result was ''ROW... Root Element Type=50331648 NameSpace='' Name='Format' Value='MQSTR '''.
2008-03-18 11:32:57.697104 31 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
valuating expression ''OutputRoot.MQMD.Format = ' ''' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '11.28'). This resol
ved to ''ROW... Root Element Type=50331648 NameSpace='' Name='Format' Value='MQSTR ' = ' '''. The result was ''FALSE
''.
2008-03-18 11:32:57.697396 31 UserTrace BIP2537I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.Fix Headers': E
xecuting statement ''RETURN TRUE;'' at ('.SF_FAILURE_ADAPTER_Fix Headers.main', '15.2').
2008-03-18 11:32:57.697752 31 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'SAP_FDG_WMMBID02_AD
APTER.SF_FAILURE_ADAPTER.Fix Headers'.
2008-03-18 11:32:57.698904 31 UserTrace BIP4201I: Message propagated to out terminal from node 'SAP_FDG_WMMBID02_AD
APTER.SF_FAILURE_ADAPTER.Reset_to_BLOB'.
A reset content descriptor node has received a message and is propagating it to any no
des connected to its out terminal.
No user action required.
2008-03-18 11:32:57.703364 31 UserTrace BIP2638I: The MQ output node 'SAP_FDG_WMMBID02_ADAPTER.SF_FAILURE_ADAPTER.D
eliberate_Failure' attempted to write a message to queue ''MQSI.QL.ADAPTER.WMMBID02.FAILURE'' connected to queue manager ''''
. The MQCC was '0' and the MQRC was '0'.
2008-03-18 11:32:57.703464 31 UserTrace BIP2622I: Message successfully output by output node 'SAP_FDG_WMMBID02_ADAP
TER.SF_FAILURE_ADAPTER.Deliberate_Failure' to queue ''MQSI.QL.ADAPTER.WMMBID02.FAILURE'' on queue manager ''''.
2008-03-18 11:33:27.387400 27 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input nod
e 'ConfigurationMessageFlow.InputNode'.
2008-03-18 11:33:27.387874 27 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Configurati
onMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2008-03-18 11:33:27.388118 27 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMess
ageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected
based on value ''MQHMD'' from previous parser.
2008-03-18 11:33:27.388666 27 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMess
ageFlow.InputNode' to handle portion of incoming message of length '236' bytes beginning at offset '364'. Parser type selecte
d based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
27 31 |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Mar 18, 2008 1:29 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I have 3 segments coming from SAP. Control rec, y segment and i segment. The i segment is a repeater. I have a message set with 3 fields for control record set to 1,1 (min occurs and max occurs) and 5 fields for y segment set to 1,1 (min occurs and max occurs) and 10 fields for the I segment set to 1, -1 (min occurs and max occurs) since its a repeater. |
Maybe it's just your wording, but that doesn't sound right to me. You should be setting maxOccurrs=-1 in exactly one place in your message definition - i.e. on the I structure itself. It sounds as if you are setting maxOccurs=-1 on 10 fields. I assume that you do have an element or group containing the 10 members of I? |
|
| Back to top |
|
|
| prk |
| Posted: Wed Mar 19, 2008 6:53 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Kimbert,
I tried that first and it didn't work. So, I declared a repeat local element before the i segment and set the max occurs to -1 and for all the 10 fields in i segment I set it to 1. I am setting this Repeats field value from my flow based on the number of times the i segment is repeating on the Input. I have 2 repeating i segments in the input msg but here is the error that it shows when I run a User trace.
FYI: The PARTNER_PROFILE field in the first field of the MRM and the one which doesn't repeat.
2008-03-19 10:45:41.140440 37 UserTrace BIP4220I: Message propagated to out terminal from node 'SAP_FDG_WMMBID02_AD
APTER.Germany'.
A label node has received a message and is propagating it to any nodes connected to it
s out terminal.
No user action required.
2008-03-19 10:45:41.211840 37 UserTrace BIP2231E: Error detected whilst processing a message in node 'SAP_FDG_WMMBI
D02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02'.
The message broker detected an error whilst processing a message in node 'SAP_FDG_WMMB
ID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02'. 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.
2008-03-19 10:45:41.211960 37 RecoverableException BIP2230E: Error detected whilst processing a message in node 'SAP
_FDG_WMMBID02_ADAPTER.MQSI.QL.TD.WMMBID02'.
The message broker detected an error whilst processing a message in node 'SAP_FDG_WMMB
ID02_ADAPTER.MQSI.QL.TD.WMMBID02'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-03-19 10:45:41.212000 37 ParserException BIP5286E: Message Translation Interface Writing Errors have occurred:
Message Set Name : ''FDG_SAP_WMMBID02'' Message Set Level : '1' Message Format : ''CWF'' Message Type Path : ''FDG_SA
P_WMMBID02''
Review further error messages for an indication to the cause of the errors.
2008-03-19 10:45:41.212124 37 ParserException BIP5167E: Custom Wire Format error while parsing/writing message ''FDG
_SAP_WMMBID02''.
2008-03-19 10:45:41.212152 37 ParserException BIP5350E: Custom Wire Format writing error. While writing the message
quoted above, the CWF writer encountered an error. The error occurred during or after the writing of element ''/FDG_SAP_WMMB
ID02/Control_Rec/PARTNER_PROFILE''.
Check that you have built the message correctly.
See following messages for more details.
2008-03-19 10:45:41.212172 37 ParserException BIP5168E: Custom Wire Format writing error.
While writing the logical tree to the bitstream, a data conversion error occurred.
The element ''77^PARTNER_PROFILE'' is either too long, or is out of range for the phys
ical data type of ''fixed-length string''.
Change the definition of the element so that it can store the data safely, or change t
he incoming message so that the element is in the correct range.
2008-03-19 10:45:41.213260 37 UserTrace BIP2540I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace': F
inished evaluating expression ''CURRENT_TIMESTAMP'' at ('', '2.9'). The result was ''TIMESTAMP '2008-03-19 10:45:41.212266'''
.
2008-03-19 10:45:41.213644 37 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace': E
valuating expression ''Root'' at ('', '4.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 N
ameSpace='' Name='Root' Value=NULL''.
2008-03-19 10:45:41.541888 37 UserTrace BIP2539I: Node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace': E
valuating expression ''ExceptionList'' at ('', '5.3'). This resolved to ''ExceptionList''. The result was ''ROW... Root Eleme
nt Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2008-03-19 10:45:41.563060 37 UserTrace BIP4067I: Message propagated to output terminal for trace node 'SAP_FDG_WMM
BID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace'.
The trace node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Trace' has received
a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2008-03-19 10:45:41.563228 37 UserTrace BIP4101I: Exception thrown by throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR
_HANDLER_ADAPTER.Throw'.
The throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw' has received
a message and will throw an exception as this is its normal behavior.
No user action required.
2008-03-19 10:45:41.591896 37 Error BIP2232E: Error detected whilst handling a previous error in node 'SAP_FDG_
WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw'.
The message broker has detected an error in node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HA
NDLER_ADAPTER.Throw' whilst handling a previous error.
See the following messages for details of the exception list associated with the origi
nal error. Thereafter messages will be associated with the new error.
2008-03-19 10:45:41.591948 37 RecoverableException BIP2230E: Error detected whilst processing a message in node 'SAP
_FDG_WMMBID02_ADAPTER.MQSI.QL.TD.WMMBID02'.
The message broker detected an error whilst processing a message in node 'SAP_FDG_WMMB
ID02_ADAPTER.MQSI.QL.TD.WMMBID02'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-03-19 10:45:41.591984 37 ParserException BIP5286E: Message Translation Interface Writing Errors have occurred:
Message Set Name : ''FDG_SAP_WMMBID02'' Message Set Level : ''1'' Message Format : ''CWF'' Message Type Path : ''FDG_
SAP_WMMBID02''
Review further error messages for an indication to the cause of the errors.
2008-03-19 10:45:41.593668 37 ParserException BIP5167E: Custom Wire Format error while parsing/writing message ''FDG
_SAP_WMMBID02''.
2008-03-19 10:45:41.593756 37 ParserException BIP5350E: Custom Wire Format writing error. While writing the message
quoted above, the CWF writer encountered an error. The error occurred during or after the writing of element ''/FDG_SAP_WMMB
ID02/Control_Rec/PARTNER_PROFILE''.
Check that you have built the message correctly.
See following messages for more details.
2008-03-19 10:45:41.593788 37 ParserException BIP5168E: Custom Wire Format writing error.
While writing the logical tree to the bitstream, a data conversion error occurred.
The element ''77^PARTNER_PROFILE'' is either too long, or is out of range for the phys
ical data type of ''fixed-length string''.
Change the definition of the element so that it can store the data safely, or change t
he incoming message so that the element is in the correct range.
2008-03-19 10:45:41.603064 37 Error BIP2628E: Exception condition detected on input node 'SAP_FDG_WMMBID02_ADAP
TER.MQSI.QL.ADAPTER.WMMBID02'.
The input node 'SAP_FDG_WMMBID02_ADAPTER.MQSI.QL.ADAPTER.WMMBID02' detected an error w
hilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work,
it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, an
d take action as described by those messages.
2008-03-19 10:45:41.603116 37 UserException BIP3001I: Exception thrown by throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ER
ROR_HANDLER_ADAPTER.Throw'; text is ''''.
The throw node 'SAP_FDG_WMMBID02_ADAPTER.SF_ERROR_HANDLER_ADAPTER.Throw' has received
a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception i
s ''''.
Since this is application generated (by message flow behavior), the user action is det
ermined by the message flow and the type of exception generated.
2008-03-19 10:46:37.427224 27 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input nod
e 'ConfigurationMessageFlow.InputNode'.
2008-03-19 10:46:37.427708 27 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Configurati
onMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2008-03-19 10:46:37.427940 27 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMess
ageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected
based on value ''MQHMD'' from previous parser.
2008-03-19 10:46:37.428488 27 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMess
ageFlow.InputNode' to handle portion of incoming message of length '236' bytes beginning at offset '364'. Parser type selecte
d based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
27 37 |
|
| Back to top |
|
|
| prk |
| Posted: Wed Mar 19, 2008 8:01 am Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Kimbert,
The issue got resolved by setting the Repeater field before the i segment. Thanks for your help. |
|
| 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
|
|
|
|
