Re: Very many MQClient queues...THANKS
Dare I suggest doing a POC(Proof of Concept) implementation to get sizing information. I'm not sure Windows is going to handle the workload you are proposing. Regards Tim A Ruzi R <[EMAIL PROTECTED]To: [EMAIL PROTECTED] M> cc: Sent by: MQSeriesSubject: Re: Very many MQClient queues...THANKS List <[EMAIL PROTECTED] N.AC.AT> 21/06/2003 00:12 Please respond to MQSeries List Thanks everyone who has responded Tim, I was told that there would be about 25 msgs/sec replies for requests. Each request would generate over 100 publications (don't know why). 25 * 100 = over 2500 msgs/sec... This was the story last year. And I just joined the project again. Some of the numbers might have changed since then. I am trying to get a better handle on this issue. I posted the question based on old numbers to get some feedback so I would sit at the bargaining table with with enough ammunition. Thanks or your response... Ruzi 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 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
Re: Very many MQClient queues...THANKS
Thanks everyone who has responded Tim, I was told that there would be about 25 msgs/sec replies for requests. Each request would generate over 100 publications (don't know why). 25 * 100 = over 2500 msgs/sec... This was the story last year. And I just joined the project again. Some of the numbers might have changed since then. I am trying to get a better handle on this issue. I posted the question based on old numbers to get some feedback so I would sit at the bargaining table with with enough ammunition. Thanks or your response... Ruzi 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
Re: Very many MQClient queues...THANKS
Ruzi Temporary dynamic queues are tailor made for your situation... It does not make sense to have 1000's of permanent queues set up for several reasons: a) Initial set up/config/running costs - cost of setting up MQ / LDAP or a DB and configuring them etc b) Maintenance costs you are going to have to maintain all of this externalized data and your application is vulnerable if you cannot access it ( server failures etc ) ... you will need to make that server highly available to avoid a single-point-of-failure arising. c) Flexibility - dynamic queues can come and go as required ... for request/reply type transactions there is rarely a need for persistent messages ... so if the queue disappears ... whats the problem? d) Scalability - you only need the reply-to-queues for the duration of active clients. e.g. If only 200 clients are active only 200 queues will be chewing up MQSeries resources as more clients connect .. more queues will be created ... so that the resources match the load. e) Authentication at the LDAP is not a reason to have these extra queues authentication is a completely separate issue. I have seen many LDAP based MQSeries systems fail because they did not consider the "SPOF" in their design. If you must externalise the queue names and make them permanent on your queue manager... make sure you have a replication LDAP server somewhere else. otherwise. :-(. It sounds like your developmemt team are potentially creating a rod for their own backs? Cheers Kevin
Re: Very many MQClient queues...THANKS
They (the dev team) are leaning more towards the perm local queues. I personally am in favour of Perm Dynamic queue per client, or one reply queue to all. I would have to do some convincing. Otherwise, we'll do it the way I explained. Thanks, Ruzi --- "O'Keeffe, Michael" <[EMAIL PROTECTED]> wrote: > Are you sure the performance for this will be better > than the other ideas > suggested on this list, i.e. using the correlation > id, temporary dynamic > queues, clusters, etc that are already provided by > MQ? > > -Original Message- > From: Ruzi R [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 17, 2003 6:57 AM > To: [EMAIL PROTECTED] > Subject: Re: Very many MQClient queues...THANKS > > > Thanks everyone who's responded. > > After getting more info from the development team, > here is how we are going to handle the clients apps: > > 1- Client app will got to LDAP for authentication > > 2- Once authenticated: > > 2.1 It will calculate its reply queue name using a > well known prefix and tag it with its machine > name. This queue name will exist. > 2.2 It will connect (not an MQ connect) to a > Special > server app running on a well known server, to > get its MQ related info among other things. It > will pass to this server app its reply queue > name and machine id. (This server app is not > introduced just because of MQ issues, it > serves > some other purposes as well that I don t want > to > get into here not that I know everything it > does). > 3- The Special server app will retrieve the required > info from a repository (LDAP or a File or an MQ > queue > or DB haven t decided yet) based on the client s > machine id. And pass this info back to the client > via > the clients reply queue > > 4- Client, having received the qmgr name and its > request queue name (among other things) from the > special server app, will connect to the qmgr and put > its message to the request queue (passing the reply > toQ and replyToQmgr name in MQMD) to the MQ App > Server > who is waiting on the Request queue > > 5-MQ App Server will process the request message > and > send the reply back as per MQMD.ReplyToQ and > MQMD.ReplyToQmgr of the request message > > 6-Client will get its replies or unsolicited > messages > from its reply queue > > Best regards, > > Ruzi > > 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 > > 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 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
Re: Very many MQClient queues...THANKS
Are you sure the performance for this will be better than the other ideas suggested on this list, i.e. using the correlation id, temporary dynamic queues, clusters, etc that are already provided by MQ? -Original Message- From: Ruzi R [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 6:57 AM To: [EMAIL PROTECTED] Subject: Re: Very many MQClient queues...THANKS Thanks everyone who's responded. After getting more info from the development team, here is how we are going to handle the clients apps: 1- Client app will got to LDAP for authentication 2- Once authenticated: 2.1 It will calculate its reply queue name using a well known prefix and tag it with its machine name. This queue name will exist. 2.2 It will connect (not an MQ connect) to a Special server app running on a well known server, to get its MQ related info among other things. It will pass to this server app its reply queue name and machine id. (This server app is not introduced just because of MQ issues, it serves some other purposes as well that I don t want to get into here not that I know everything it does). 3- The Special server app will retrieve the required info from a repository (LDAP or a File or an MQ queue or DB haven t decided yet) based on the client s machine id. And pass this info back to the client via the clients reply queue 4- Client, having received the qmgr name and its request queue name (among other things) from the special server app, will connect to the qmgr and put its message to the request queue (passing the reply toQ and replyToQmgr name in MQMD) to the MQ App Server who is waiting on the Request queue 5-MQ App Server will process the request message and send the reply back as per MQMD.ReplyToQ and MQMD.ReplyToQmgr of the request message 6-Client will get its replies or unsolicited messages from its reply queue Best regards, Ruzi 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 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
Re: Very many MQClient queues...THANKS
Thanks everyone who's responded. After getting more info from the development team, here is how we are going to handle the clients apps: 1- Client app will got to LDAP for authentication 2- Once authenticated: 2.1 It will calculate its reply queue name using a well known prefix and tag it with its machine name. This queue name will exist. 2.2 It will connect (not an MQ connect) to a Special server app running on a well known server, to get its MQ related info among other things. It will pass to this server app its reply queue name and machine id. (This server app is not introduced just because of MQ issues, it serves some other purposes as well that I don t want to get into here not that I know everything it does). 3- The Special server app will retrieve the required info from a repository (LDAP or a File or an MQ queue or DB haven t decided yet) based on the client s machine id. And pass this info back to the client via the clients reply queue 4- Client, having received the qmgr name and its request queue name (among other things) from the special server app, will connect to the qmgr and put its message to the request queue (passing the reply toQ and replyToQmgr name in MQMD) to the MQ App Server who is waiting on the Request queue 5-MQ App Server will process the request message and send the reply back as per MQMD.ReplyToQ and MQMD.ReplyToQmgr of the request message 6-Client will get its replies or unsolicited messages from its reply queue Best regards, Ruzi 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
