| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| GetbyCorrelId problem in MQGET Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| Gemz |
 Posted: Thu Aug 05, 2010 10:09 pm Post subject: GetbyCorrelId problem in MQGET Node |
 |
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
Hi,
We are trying to get a message from the queue using Get by correlID in MQGET node. But we are not able to get the message from queue.
Env : AIX, WMB 6.1.0.3
| Quote: |
Message flow looks like
MQ InputNode ---> Compute Node1 ---> MQOutput Node1 ---> MQGET Node ----> ComputeNode2 ---> MQ Output Node2 |
We tried the below options.
1. Enabled the Get by correlation ID check box in MQGET node.
2. SET the below values in the Compute Node1
SET OutputRoot.Properties.ReplyIdentifier = InputRoot.MQMD.MsgId;
SET OutputRoot.MQMD.CorrelId = InputRoot.MQMD.MsgId;
3. SET the below LocalEnvironment in the Compute Node1
SET OutputLocalEnvironment.MQ.GET.MQGMO.MatchOptions = MQMO_MATCH_CORREL_ID;
I am getting the below exception in Usertrace
| Quote: |
4424 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'MainScreeningFlow_new.BlockedInquiry.AuditRequest'.
2010-08-06 08:18:48.977204 4424 UserTrace BIP2638I: The MQ output node 'MainScreeningFlow_new.BlockedInquiry.GET.STATUS.QUEUE' attempted to write a message to queue ''GET.STATUS.QUEUE'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2010-08-06 08:18:48.977228 4424 UserTrace BIP2622I: Message successfully output by output node 'MainScreeningFlow_new.BlockedInquiry.GET.STATUS.QUEUE' to queue ''GET.STATUS.QUEUE'' on queue manager ''''.
2010-08-06 08:18:48.977372 4424 UserTrace BIP2543I: Node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE': ('', '1.1') : Failed to navigate to path element number '2' because it does not exist.
2010-08-06 08:18:48.977404 4424 UserTrace BIP4635I: The MQ Get node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE' failed to navigate to the default location ''InputLocalEnvironment.MQ.GET'' for ''Input MQ Parameters Location''.
Location ''InputLocalEnvironment.MQ.GET'' is the default value for ''Input MQ Parameters Location'' and it was not found. It is assumed that this ''Input MQ Parameters Location'' node property is not needed in this case and, therefore, the issue is ignored.
Ignore this message (and the previous user trace message regarding this navigation, if there is one) if this ''Input MQ Parameters Location'' node property is not needed; Otherwise, make sure the location is available or correct the location specification.
2010-08-06 08:18:48.977720 4424 UserTrace BIP2231E: Error detected whilst processing a message in node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE'.
The message broker detected an error whilst processing a message in node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE'. 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.
2010-08-06 08:18:48.977748 4424 RecoverableException BIP4632E: MQ Get node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE' was unable to obtain MsgId/CorrelId for message matching from input MQMD location: 'InputRoot.MQMD'.
When 'Get by Message ID'/'Get by Correlation ID' node properties are selected, a valid MQMD must be provided in the input message to MQ Get node at the location specified by the 'Input MQMD Location' node attribute.
Examine the 'Get by Message ID'/'Get by Correlation ID' and 'Input MQMD Location' node attributes to ensure that they are correctly specified and the input message to the node has the right structure. Check the following exception output, if any, for more details about the problem.
2010-08-06 08:18:48.977780 4424 UserTrace BIP4101I: Exception thrown by throw node 'MainScreeningFlow_new.BlockedInquiry.Throw'.
The throw node 'MainScreeningFlow_new.BlockedInquiry.Throw' has received a message and will throw an exception as this is its normal behavior.
No user action required.
2010-08-06 08:18:48.978824 4424 Error BIP2232E: Error detected whilst handling a previous error in node 'MainScreeningFlow_new.BlockedInquiry.Throw'.
The message broker has detected an error in node 'MainScreeningFlow_new.BlockedInquiry.Throw' whilst handling a previous error.
See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
2010-08-06 08:18:48.978836 4424 RecoverableException BIP2230E: Error detected whilst processing a message in node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE'.
The message broker detected an error whilst processing a message in node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-08-06 08:18:48.978844 4424 RecoverableException BIP4633E: An error occured whilst performing an MQGet node operation.
N/A.
See the following messages for information pertaining to this error.
2010-08-06 08:18:48.978852 4424 RecoverableException BIP4632E: MQ Get node 'MainScreeningFlow_new.BlockedInquiry.MQGET.REPLY.QUEUE' was unable to obtain MsgId/CorrelId for message matching from input MQMD location: 'InputRoot.MQMD'.
When 'Get by Message ID'/'Get by Correlation ID' node properties are selected, a valid MQMD must be provided in the input message to MQ Get node at the location specified by the 'Input MQMD Location' node attribute.
Examine the 'Get by Message ID'/'Get by Correlation ID' and 'Input MQMD Location' node attributes to ensure that they are correctly specified and the input message to the node has the right structure. Check the following exception output, if any, for more details about the problem.
2010-08-06 08:18:48.979440 4424 Error BIP2628E: Exception condition detected on input node 'MainScreeningFlow_new.INPUT.REQUEST.QUEUE'.
The input node 'MainScreeningFlow_new.INPUT.REQUEST.QUEUE' detected an error whilst 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, and take action as described by those messages.
2010-08-06 08:18:48.979452 4424 UserException BIP3001I: Exception thrown by throw node 'MainScreeningFlow_new.BlockedInquiry.Throw'; text is ''''.
The throw node 'MainScreeningFlow_new.BlockedInquiry.Throw' has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is ''''.
Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.
2010-08-06 08:18:49.992764 4424 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'MainScreeningFlow_new.INPUT.REQUEST.QUEUE'.
Node 'MainScreeningFlow_new.INPUT.REQUEST.QUEUE' 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 exceeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the message 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.
2010-08-06 08:18:49.993120 4424 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'MainScreeningFlow_new.INPUT.REQUEST.QUEUE' to handle portion of incoming message of length 0 bytes beginning at offset '0'. |
_________________
GemZ
"An expert is one who knows more and more about less and less until he knows absolutely everything about nothing...." |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Aug 06, 2010 12:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You need to have a compute node between the MQOutput node and the MQGet node. The messageId and correlationId can be found in the LocalEnvironment (Check the documentation of the MQOutput node).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Fri Aug 06, 2010 1:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| What is the 'Transaction Mode' property of the MQOutput Node1? It should probably be "No". |
|
| Back to top |
|
|
| Gemz |
| Posted: Fri Aug 06, 2010 3:57 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
Hi rekarm01,
Yes, you are correct. Transaction Mode' property of the MQOutput Node1 is 'NO'.
_________________
GemZ
"An expert is one who knows more and more about less and less until he knows absolutely everything about nothing...." |
|
| 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
|
|
|
|
