Hello Steve:

I feel this is quite difficult design problem for the MQSeries. I am not sure what 
MQSeries Pub/Sub is (we use another MOM for publish/subscribe problems) but you might 
want to check if it supports any kind of multicast -- if it does, consider using it. 
Otherwise, multiple queues sound much better to me, especially if the publisher has 
enough information to set the proper correlation ID for the client: In this case, you 
might want to create queues on demand from publishers using PCF messages and have one 
"signalling" queue for clients to learn about the names of their respective queues. In 
this case, the administrator will not have much to be unhappy about (except for the 
security, of course, but that would be another question... :-)).

Have a nice day,
Pavel





                      Steve Muller
                      <[EMAIL PROTECTED]>        To:       [EMAIL PROTECTED]
                      Sent by: MQSeries        cc:
                      List                     Subject:  One or Many reply queues for 
Clients?
                      <MQSERIES@AKH-Wie
                      n.AC.AT>


                      07/05/2002 11:17
                      AM
                      Please respond to
                      MQSeries List






Hi all,

Part of our MQ environment is OS/390 (2.1) and NT
(5.2). We will have about 190 NT clients connected to
OS/390. These NT client apps will send a request and
get their replies from OS/390, based on a correlid.
More than 90% of these requests will be queries. We
are estimating that, for all the 190 clients combined,
 there will be about 50 requests and  roughly
50-10000 replies per sec. The turn-around time is
expected  by the user to be 2-12 sec based on the
importance of the request.

I am thinking that we can have either:
1-      One reply queue that would be serviced by all the
clients, OR
2-      A dedicated reply queue for each client.

In the scenario 1:  I know that a  qualified GET
would be slower from a queue with a high Q-depth (I
know indexing could be used ). As far as I can see,
the major downside to this approach would be if
something goes wrong with this queue all the clients
would suffer.

In  the scenario 2: If we have a dedicated reply queue
for each client, MQ admin would not be very happy but
the retrieval of the  msgs would be faster (even if we
used qualified Gets). And a problem with one queue
would not effect the rest of the reply queues


What do you think?   Your insights would be much
appreciated.

Regards,

Steve




__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive




--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to