ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MSG EXPIRATION

Post new topic  Reply to topic
 MSG EXPIRATION « View previous topic :: View next topic » 
Author Message
kavithadhevi
PostPosted: Tue May 20, 2003 7:38 am    Post subject: MSG EXPIRATION Reply with quote

Master

Joined: 14 May 2002
Posts: 201
Location: USA

Heres a situation, I have an expiration for the message and which will be reported with a EXPIRATION_WITH_FULL DATA. As far as message is concerned when it expires it puts on a different Q mentioned in the ReplyToQ, thats cool, but say my application wants to use a ReplyToQ with a different Q . In this context, i want to seperate the expired message to a different Q and the original message to send a message back using the ReplyToQ.
I would like to get some suggestions to achieve this. Any thoughts.
_________________
Thanks in Advance.

Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mqonnet
PostPosted: Tue May 20, 2003 12:35 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

I am sorry, but this one got me.!!!

I went through your post no less than 6 times, but could not understand what you want to achieve.

When you put a message onto a queue requesting a report you specify a replytoq in your app. This is the queue where the expiration report is sent. You start with your original message. If it is not retrieved within the time set for expiration, the message expires and a report is generated on the next browse/destructive get. This report is sent to the replytoq.

There is no other processing or queues involved.

Hope this helps.

Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
jefflowrey
PostPosted: Tue May 20, 2003 12:55 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

What he's asking about is setting a DIFFERENT queue for reports than for normal replies.

So,
Case 1) Message is processed normally. Reply message goes to ReplyQ1
Case 2) Message is not processed, and expires. Report message goes to ReplyQ2.

I don't think he can do this at the MQSeries level. What he could do is something like this: Set ReplyQ to something like "ReplyToQueue.Report", and have his application determine that when it needs to generate a reply it should put the reply to "ReplyToQueue" (dropping the ".Report" from the queue name). This allows the normal flexibility of a regular request/reply, where the requesting app determines where the reply goes, while still doing what he wants. Of course, then his application is not fully following the recommended practices for request/reply.

The other option is to put a filter process between his reply queue and his reply process. So, both the report and reply messages go to the same ReplyToQueue. That queue is read by something that routes Report messages to a different queue.
Back to top
View user's profile Send private message
Chris123
PostPosted: Tue May 20, 2003 11:28 pm    Post subject: Reply with quote

Novice

Joined: 14 Apr 2003
Posts: 11

Jeff is right with his interpretation of the original question. Personally I find this the most annoying feature of MQ, and it seems a huge oversight. What Kavitha wants is what MSMQ calls Administrations queues. This logical separation then leaves it up to the person sending the request message to decide if the Administration queue should then be the same as the ReplyTo Queue or not. Otherwise you have to perform some kludge like Jeff suggests, which involves the application responding to the request having some knowledge about naming conventions. This is of course impractical in a real world scenario when interfacing to a client's host system that was written say five years ago, by a group of people who have since left, and where you are only one of many clients. [aaah! rant over.]
Back to top
View user's profile Send private message
kavithadhevi
PostPosted: Fri May 23, 2003 5:54 am    Post subject: Reply with quote

Master

Joined: 14 May 2002
Posts: 201
Location: USA

Thanks a lot for sharing your views. I guess i have handle this option from the application side.
I really appreciate your postings.
_________________
Thanks in Advance.

Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MSG EXPIRATION
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.