Thanks Paul: I 100% agree with the most of your e-Mail. NT threads are really good and worth to use instead of processes (they could even provide a complete isolation of clients in security terms if MQSeries had some interface for it). But here is the scenario that bothers me from time to time:
1. The distributed application wants to use MQSeries natural message sequence. All conditions are satisfied, including not having any dead letter queues. 2. Due to the slow subscriber the queue becomes full. 3. Channel stops in accordance with the documentation. My question is, will this channel stop affect other applications communicating via the same listener process with different queues? If the answer is yes, then I know why some users might want separate processes for their channels even on MQSeries NT :-). Thank you, Pavel ---------------------------------------- Message History ---------------------------------------- From: Paul Clarke <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 06/21/2002 12:06 PM CET Please respond to MQSeries List <[EMAIL PROTECTED]> DELEGATED - Sent by: MQSeries [EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Non threaded listener on Windows >Paul, >Thanks for the explanation. >So I was right there is no way to run channel agent as a process on NT? >Except if I run several listeners and enforce a single connection per listener via Exit :-)? >Thank you, >Pavel Pavel, The non-threaded listener would be inetd right ? Since Windows does not come with an inetd process (as such) we have not had a strong requirement to support this mode of operation. Usually users want to run channels as separate processes either for testing purposes or for scalability (ie. huge numbers of clients). On NT a single listener is quite capable of handling a large number of clients. For testing a dodgy channel exit (or whatever), you are right, I would recommend that you start your channel into a different listener listening on a different port. As a general rule though I do not recommend that each channel requires it's own listener. It should only be on test systems or when testing a new channel exit or similar that you might feel the need to isolate one channel from all the others. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley 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
