Inetd for more than a couple of hundred connections is usually more reliable. Runmqlsr and threads uses less resources. As for your second question its determined by which type of listener you use. To quote from the manual.
You can use inetd or the Run Listener (RUNMQLSR) command to define a TCP/IP
connection on a UNIX systerm server, . If you use inetd, a process sis
started for each connection you define. If you use the RUNMQLSR command, a
thread is started for each connection. This method can therefore be more
efficient.
I have seen both working well on small systems, however for systems that
have several thousand client connections we use inetd.
Regards
Tim A
"Stephan C. Moen"
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: MQSeries cc:
List Subject: SWOT Analysis with listeners
as inetd or runmqlsr AND channels as
<[EMAIL PROTECTED] threads or processes
N.AC.AT>
15/03/2003 16:03
Please respond to
MQSeries List
MQSeries Experts,
I am inquiring from the vast array of knowledge within the MQSeries
community on two simple topics. Please respond to the strengths and
weaknesses of the following.
1) Choice of listener: inetd or runmqlsr process.
2) Choice of channel: start as a thread or process.
I’m not looking for book responses, just REAL-LIFE experiences, especially
from a performance, reliability, scalability, and MQSeries Version (5.3,
5.2 and below) perspective. Thank you.
Steve Moen
kb{ " XX˛بަ/ם{axǫgzRǫkuj)ZnWm
l\`+rzm!'iƭz܆+
