| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Expiry on Reply Messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| djfox |
 Posted: Thu May 29, 2008 6:38 am Post subject: Expiry on Reply Messages |
 |
|
Novice
Joined: 24 Feb 2007
Posts: 12
Location: Maryland
|
Hopefully, someone can come up with an answer to my problem. I have a flow: HTTPInput->Compute1->MQOutput->MQGet->Compute2->HTTPReply. The flow is being used to expose a Web Service that registers durable subscribers. In the Compute1 node I set the following:
SET OutputRoot.MQMD.ReplyToQ = 'TEST.REPLYTO';
SET OutputRoot.MQMD.ReplyToQMgr = 'WBRK_QM';
SET OutputRoot.MQMD.Expiry = 720;
SET OutputRoot.MQMD.Report = MQRO_PASS_CORREL_ID + MQRO_PAN + MQRO_NAN;
The intent is to have the message broker send a subscription status reply message that will be reformatted in Compute2, and sent back to the requester. The problem I'm having is that I want to set the expiry on the reply message (to keep the queue clear). I've read the infocenter, and it indicates that expiry is one of the fields that is copied to the reply message. However, when I look at the status message the expiry is set to -1 (unlimited). I've also tried to set Properties.ExpirationTime, but that didn't help. What did happen was the subscription timeout was set. So, how do I set the expiry on the status reply message, and not the subscription timeout? |
|
| Back to top |
|
 |
| francoisvdm |
| Posted: Mon Jun 02, 2008 1:23 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
I ran into this same problem...if your message flow is started with a HTTP node then you can't set expiry...I've tried in so many different ways. If you start a message flow with an MQ input node it does work 100% if you use
SET OutputRoot.Properties.ExpirationTime = 720;
I do not know if this is a bug or something, but up to now I could not get it to work.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| djfox |
| Posted: Mon Jun 02, 2008 9:50 am Post subject: Expiry on Reply Messages |
|
|
Novice
Joined: 24 Feb 2007
Posts: 12
Location: Maryland
|
Interesting. I wonder why it would work with an MQInput node and not
an HTTPInput node. My code basically sets all of the MQMD properties,
plus I set the SET ALL properties on the MQOutput node. Per your note
I tried using:
SET OuputRoot.Properties.ExpirationTime = 720;
But I get the same result: the reply message has an expiry of -1 and
the subscriptions expires after one minute (720 tenths). |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Mon Jun 02, 2008 9:30 pm Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Yes, I know, will only work if MQInput node is starting the flow...try that. I've compared my output msg byte for byte between MQInput node and HTTPInput node...no difference that I could see and it still gave that same problem. Search for my other posts on this, there was another VERY funny involved....if I remember correctly it would start the first msg with a very big expiry value, no matter what you set and that all subsequent messages will have the "remainder" of the time until message flow was running for a long time .... and then expiry would work correctly.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| 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
|
|
|
|
