MQSeries.net :: View topic - Channels & listeners–trusted & not trusted

KAKEZ

Hi,

I would like to get advices of all of mqseries specialists about the following questions because that’s not yet clear for me:

1 – concerning message channels
+++++++++++++++++++++

11 – at the sending end

> for each channel of type: SDR, SVR, RQSTR, CLUSSDR, CLUSRCVR – only -

*** it is possible to start the channel as a process or a tread depending on the value of the channel attribute MCATYPE - value = PROCESS or THREAD

BUT this only on Unix platform -> so on Windows platforms the only way to start such channels as threads is starting them using a channel initiator – which will start the channel as a thread of itself
and
on Windows if we start such channels via runmqchl command, the MCA will always be a process, nevae a thread,
 right ?

*** if we code MCATYPE(THREAD) the MCA will be started as thread but thread of what?

+ if the channel is started automatically by a channel initiator the MCA will be a thread of the
channel initiator process?

+ but if the channel is started by the command ‘runmqchl’ (for SDR & RQSTR) the MCA will be a
thread of which process – if that is possible?

12 – at the receiving end

> on Windows platforms because the only listener available is runmqlsr, each receiving channel (RCVR, SVRCONN) will be started as thread of it?

> on Unix platforms we have the choice between two listeners (inetd or runmqlsr)

- with inetd the MCA is always started as a process named amqrsta? Even if the MCATYPE attribute is (THREAD)?

- with runmqlsr the MCA is always started as a thread of it – evan if the MCATYPE attribute is PROCESS?

2 – concerning MQI channels
++++++++++++++++++
21 – at the receiving end: SVRCONN (unix server)

> so a SVRCONN channel is always a process, never a thread because the MCATYPE attribute is not available for it – right?

3 – concerning TCP/IP params at the server platform
+++++++++++++++++++++++++++++++++
I noticed that:

31 - to define the TCP/IP connection you must declare within the /etc/services the different port numbers on which the server listeners have to listen for MQSeries requests like:
MQSeries1 1414/tcp
MQSeries2 1415/tcp

If we have for instance two qmgrs QM1 & QM2 each of one having a listerner listening the first on port 1414 and the other on port 1415 – right?

- if not doing that you cannot handle MQSeries channels on TCP/IP?

32 – which listener to use ?

> question is only for Unix platforms because on Windows platforms the only TCP/IP listener available is ‘runmqlsr’ – right?

if we want to use the unix listener ‘inetd’
********************************
- we must define within the inetd.conf file the lines:
MQSeries1 stream tcp nowait mqm /opt/mqm/bin/amqcsta amqrsta –m QM1
MQSeries2 stream tcp nowait mqm /opt/mqm/bin/amqcsta amqrsta –m QM2
right?

- in that case the inetd listener is listening all the MQSeries ports – here 1414 and 1415?

- does the inetd listener start a process amqrsta (receiver MCA) each time it receives a start request from the corresponding sender MCA?

- in that case even for a SVRCONN channel the MCA started is a process named amqrsta?

- in that case we can have a lot of amqcrsta processes running at the same time if we have many inbound channels on the server?

- plus: each amqrsta is a process not a thread of inetd

- it is easy to display and see (ps –ef) all the MCA receivers running because each one corresponds to one amqrsta process?

if we want to use only the MQSeries listener ‘runmqlsr’ like:
***********************************************
runmqlsr –t tcp –p 1414 –m QM1
runmqlsr –t tcp –p 1415 –m QM2

- do we also have to define lines within the inetd.conf file?
normally not because we don’t use the unix listener!

- runmqlsr starts each MCA receiver as a thread of it, so:

+ we cannot display and see each MCA receiver ?
that is important question when we have generic channel (RCVR or SVRCONN channels)
and we want for exemple stop a specific channel among all of them: how to isolate the
channel we want to stop ans on what criteria can we choose it?

+ is it possible anyway to know what are all these threads?

+ do all these runmqlsr’s threads keep running even the “father” runmqlsr crashes or do they carry on running by themthelves? – important question is : if one runmqlsr listener has started/is handling say 200 connections, when it crashes do all these 200 threads handling the connections also crash or they keep running?

- is that also true when the runmqlsr listener start a SVRCONN MCA?

- do you recommend to have several runmqlsr listeners at the same time listening on different port numbers in case of a great number of concurrent connections (say 400)?

- I have heard that runmqlsr is better than inetd in term of performance and is the listener IBM recommends to use on unix platforms – any experience about that?

- also runmqlsr is able to start the receiver MCA as trusted channel which is not possible with inetd!

is it possible to use both listeners - unix: ‘inetd’ and MQSeries: ‘runmqlsr’?
**********************************************************
- in that case is it possible to specify somewhere the port number we want inetd listen to? 1515
if we only start runmqlsr on 1414 port as: runmqlsr –t tcp –p 1414 –m QM1

thanks for advices
Jack