| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| RFH1 Publications and Replies |
« View previous topic :: View next topic » |
| Author |
Message
|
| ccrandall |
 Posted: Thu Jul 30, 2009 9:44 am Post subject: RFH1 Publications and Replies |
 |
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
I'm running into an issue where our framework is trying to publish a RFH1 message, however, in this particular instance there aren't any RFH1 subscribers for this topic. When this message is sent to the Publication node, even though there are no subscribers it's trying to send a response message.
The RFH1 message is marked as a datagram with no replyToQ in the MQMD. So, the response is going to SYSTEM.DEAD.LETTER.QUEUE. Is this the correct behavior? I was under the impression that if there were no subscribers that the Publication node would just toss away the message and that was the end of it. Or does it still need a replyToQ to send a response (similar to using SYSTEM.JMS.REPORT.QUEUE in the case where it's a RFH2/JMS message)?
Below is the trace of the Publication node:
BIP7080I: Node 'abc.reqFlow.putRequest.publishMsgs.PublicationRFH1.ComIbmPSService': The Publication Node with Subscription Point '''' has received a message of type 'Publish'.
The Publication Node with Subscription Point '''' has started processing a message.
No user action required.
BIP7085I: Node 'abc.reqFlow.putRequest.publishMsgs.PublicationRFH1.ComIbmPSService': The Publication Node has propagated a message to its output terminal for subscription point ''''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
BIP7085I: Node 'abc.reqFlow.putRequest.publishMsgs.PublicationRFH1.ComIbmPSService': The Publication Node has propagated a message to its output terminal for subscription point ''''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
BIP2638I: The MQ output node 'abc.reqFlow.putRequest.publishMsgs.PublicationRFH1.Response' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''QMGR1''. The MQCC was '0' and the MQRC was '0'.
Thanks! |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Thu Jul 30, 2009 10:56 am Post subject: Re: RFH1 Publications and Replies |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Are you sure you dont have an MQOutput node (rather than the publish node causing this behaviour) in the flow thats making the message get written to the DLQ? It may be me misreading the trace but this is why I think this is the case....
| ccrandall wrote: |
BIP2638I: The MQ output node 'abc.reqFlow.putRequest.publishMsgs.PublicationRFH1.Response' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''QMGR1''. The MQCC was '0' and the MQRC was '0'.
Thanks! |
I'm guessing you have a setting (cant remember the exact one but it was discussed on here about 3 weeks ago and is in the documentation) on the node set to make it use the replytoqueue from the message which then makes it go to the DLQ as there is no replytoq set. Whats the DLH reason code. 2085 by chance? |
|
| Back to top |
|
|
| ccrandall |
| Posted: Thu Jul 30, 2009 11:58 am Post subject: |
|
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
I'm looking at the flow and the publication node is at the end of the chain. After it executes, it's going back to a flow order node and executing logic in a filter node. I see that in the trace immediately after the chunk I posted previously. So, unless I'm ignorant about how these flows work (which is possible, I'm still a bit new to this), I don't see any intervining MQOutput nodes that should be called immediately after the publication node runs.
Looking at the properties of the publication node, it just has the node name set in the description. The subscription point is blank and the implicit stream naming box is unchecked.
Looking at the DLH, I have a reason code of 65536. The whole message is below:
<MQMD>
<Format>MQDEAD</Format>
<Expiry>-1</Expiry>
<Persistence>PERSISTENT</Persistence>
<ReplyToQueueName></ReplyToQueueName>
<ReplyToQueueManagerName>BROKERP1</ReplyToQueueManagerName>
<Userid>mqsi</Userid>
<PutApplicationName>DataFlowEngine</PutApplicationName>
<PutDateTime>07-13-2009 10:51:09</PutDateTime>
<MessageId>414D512046454D3036425031202020204A35152C2216FBDA</MessageId>
<CorrelationId>414D51204D4152434F202020202020204A34FF8B231873AE</CorrelationId>
<Priority>4</Priority>
<BackoutCount>0</BackoutCount>
<AccountingToken>[B@64a53d1</AccountingToken>
<ApplicationIdData></ApplicationIdData>
<Feedback>0</Feedback>
<Encoding>273</Encoding>
<CharacterSet>819</CharacterSet>
<MsgType>2</MsgType>
<PutApplicationType>UNIX</PutApplicationType>
</MQMD>
<DLH>
<StrucId>DLH</StrucId>
<Version>1</Version>
<Encoding>273</Encoding>
<CodedCharSetId>819</CodedCharSetId>
<Format>MQHRF</Format>
<Reason>65536</Reason>
<DestQName></DestQName>
<DestQMgrName>QMGR1</DestQMgrName>
<PutApplType>6</PutApplType>
<PutApplName>WebSphereMQIntegrator6</PutApplName>
<PutDate>20090713</PutDate>
<PutTime>15510900</PutTime>
</DLH>
<MSGBODY>
RFH ^AX^A^Q^C3 MQPSCompCode 0 MQPSReason 0 MQPSReasonText MQRC_NONE
</MSGBODY>
Thanks! |
|
| 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
|
|
|
|
