Re: Connecting to more than one queue managers on solaris, linux
Thanks eugene, Probably, not in 5.3. This is the error we are getting on Solaris: 2103( MQRC_ANOTHER_Q_MGR_CONNECTED) Child processes would be one option -- but it was decided against it for non-MQ-related reasons. Thanks, Pavel eugene rosenberg [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COMcc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/02/2004 08:46 PM Please respond to MQSeries List Pavel, It was always possible to have connections to various queue managers from UNIX child processes (still one connection per child process) and I did it myself. In the best of my knowledge starting with V5.2 it became possible to have the same type of connections from threads. Even I did not try it myself I am using products that are multithreaded and each thread has it is own connection. In some cases the number of threads is directly defined by the number of local queue managers. Eugene --- Pavel Tolkachev [EMAIL PROTECTED] wrote: Well, for a loopback interface (I mean, when client connects to localhost or 127.0.0.1), it should not call real network drivers. I think it uses some platform-specific IPCs (on solaris, probably streams -- I believe both pipes and local sockets use same underlying mechanisms, on very old Unices it were mbufs) -- and should not be really heavy... Although, the latency will increase due to the agent and some overhead will still be there.. Even when real IP is used, smart TCP stack must not hit the network for local connections. Just thinking aloud.. I have never really tested it with MQ but I did some performance testing with locally bound TCP sockets -- as long as all socket options were set right (especially TCP_NDELAY), the overhead became negligible. Hopefully, IBM got it right :-). Just my 2c Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/01/2004 02:39 PM Please respond to MQSeries List The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using
Re: Connecting to more than one queue managers on solaris, linux
But I understood the question was restricted to an application writing to a local queue using local bindings vrs client bindings (i.e., no transmission queue involved). In that case, I think local bindings would always have a performance advantage. The situation for a distributed environment would be much different. And, yes, yes, really tricky. You'd more-often-than-not need to take measurements to know for sure. -Original Message- From: eugene rosenberg [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Dennis, It is really tricky to compare client/server performance with server/server performance. I agree that each application MQ client call would lose in performance compare with application MQ server call but I believe that the total throughput is better with the client/server communication because the number of I/O is low. The message is going directly to destination queue within client/server without be placed and retrieve on/from transmission queue. Eugene --- Miller, Dennis [EMAIL PROTECTED] wrote: The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond
Re: Connecting to more than one queue managers on solaris, linux
Agree --- Miller, Dennis [EMAIL PROTECTED] wrote: But I understood the question was restricted to an application writing to a local queue using local bindings vrs client bindings (i.e., no transmission queue involved). In that case, I think local bindings would always have a performance advantage. The situation for a distributed environment would be much different. And, yes, yes, really tricky. You'd more-often-than-not need to take measurements to know for sure. -Original Message- From: eugene rosenberg [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Dennis, It is really tricky to compare client/server performance with server/server performance. I agree that each application MQ client call would lose in performance compare with application MQ server call but I believe that the total throughput is better with the client/server communication because the number of I/O is low. The message is going directly to destination queue within client/server without be placed and retrieve on/from transmission queue. Eugene --- Miller, Dennis [EMAIL PROTECTED] wrote: The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers
Re: Connecting to more than one queue managers on solaris, linux
Pavel, I will do some research next week. I assume it should work in 5.3. I mentioned product that I am currently using. It is MQ system management product. Several components of it are multithreaded and are keeping connections to all active local queue managers. And I am using it in multithreaded mode on several platforms including SUN Solaris. Eugene --- Pavel Tolkachev [EMAIL PROTECTED] wrote: Thanks eugene, Probably, not in 5.3. This is the error we are getting on Solaris: 2103( MQRC_ANOTHER_Q_MGR_CONNECTED) Child processes would be one option -- but it was decided against it for non-MQ-related reasons. Thanks, Pavel eugene rosenberg [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COMcc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/02/2004 08:46 PM Please respond to MQSeries List Pavel, It was always possible to have connections to various queue managers from UNIX child processes (still one connection per child process) and I did it myself. In the best of my knowledge starting with V5.2 it became possible to have the same type of connections from threads. Even I did not try it myself I am using products that are multithreaded and each thread has it is own connection. In some cases the number of threads is directly defined by the number of local queue managers. Eugene --- Pavel Tolkachev [EMAIL PROTECTED] wrote: Well, for a loopback interface (I mean, when client connects to localhost or 127.0.0.1), it should not call real network drivers. I think it uses some platform-specific IPCs (on solaris, probably streams -- I believe both pipes and local sockets use same underlying mechanisms, on very old Unices it were mbufs) -- and should not be really heavy... Although, the latency will increase due to the agent and some overhead will still be there.. Even when real IP is used, smart TCP stack must not hit the network for local connections. Just thinking aloud.. I have never really tested it with MQ but I did some performance testing with locally bound TCP sockets -- as long as all socket options were set right (especially TCP_NDELAY), the overhead became negligible. Hopefully, IBM got it right :-). Just my 2c Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/01/2004 02:39 PM Please respond to MQSeries List The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single
Re: Connecting to more than one queue managers on solaris, linux
Yes, the question was about a local app. Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/03/2004 05:11 PM Please respond to MQSeries List But I understood the question was restricted to an application writing to a local queue using local bindings vrs client bindings (i.e., no transmission queue involved). In that case, I think local bindings would always have a performance advantage. The situation for a distributed environment would be much different. And, yes, yes, really tricky. You'd more-often-than-not need to take measurements to know for sure. -Original Message- From: eugene rosenberg [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Dennis, It is really tricky to compare client/server performance with server/server performance. I agree that each application MQ client call would lose in performance compare with application MQ server call but I believe that the total throughput is better with the client/server communication because the number of I/O is low. The message is going directly to destination queue within client/server without be placed and retrieve on/from transmission queue. Eugene --- Miller, Dennis [EMAIL PROTECTED] wrote: The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several
Re: Connecting to more than one queue managers on solaris, linux
Thanks Eugene, Yes, please let us know your findings. For system management, you may either use the client (the way I do not like), or connect/disconnect each time (the one we have now), or spawn multiple processes or connect to a single QM (you can use dedicated admin qm for that -- another way I kind of fond of) and use intercommunications for others. The options are plenty which by itself tells that no one of them is perfect... Pavel eugene rosenberg [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COMcc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/03/2004 06:21 PM Please respond to MQSeries List Pavel, I will do some research next week. I assume it should work in 5.3. I mentioned product that I am currently using. It is MQ system management product. Several components of it are multithreaded and are keeping connections to all active local queue managers. And I am using it in multithreaded mode on several platforms including SUN Solaris. Eugene --- Pavel Tolkachev [EMAIL PROTECTED] wrote: Thanks eugene, Probably, not in 5.3. This is the error we are getting on Solaris: 2103( MQRC_ANOTHER_Q_MGR_CONNECTED) Child processes would be one option -- but it was decided against it for non-MQ-related reasons. Thanks, Pavel eugene rosenberg [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COMcc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/02/2004 08:46 PM Please respond to MQSeries List Pavel, It was always possible to have connections to various queue managers from UNIX child processes (still one connection per child process) and I did it myself. In the best of my knowledge starting with V5.2 it became possible to have the same type of connections from threads. Even I did not try it myself I am using products that are multithreaded and each thread has it is own connection. In some cases the number of threads is directly defined by the number of local queue managers. Eugene --- Pavel Tolkachev [EMAIL PROTECTED] wrote: Well, for a loopback interface (I mean, when client connects to localhost or 127.0.0.1), it should not call real network drivers. I think it uses some platform-specific IPCs (on solaris, probably streams -- I believe both pipes and local sockets use same underlying mechanisms, on very old Unices it were mbufs) -- and should not be really heavy... Although, the latency will increase due to the agent and some overhead will still be there.. Even when real IP is used, smart TCP stack must not hit the network for local connections. Just thinking aloud.. I have never really tested it with MQ but I did some performance testing with locally bound TCP sockets -- as long as all socket options were set right (especially TCP_NDELAY), the overhead became negligible. Hopefully, IBM got it right :-). Just my 2c Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/01/2004 02:39 PM Please respond to MQSeries List The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one
Re: Connecting to more than one queue managers on solaris, linux
Dennis, It is really tricky to compare client/server performance with server/server performance. I agree that each application MQ client call would lose in performance compare with application MQ server call but I believe that the total throughput is better with the client/server communication because the number of I/O is low. The message is going directly to destination queue within client/server without be placed and retrieve on/from transmission queue. Eugene --- Miller, Dennis [EMAIL PROTECTED] wrote: The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeries Subject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel
Re: Connecting to more than one queue managers on solaris, linux
What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available
Re: Connecting to more than one queue managers on solaris, linux
Most, if not all, monitoring products use a local agent that runs as a server-side MQ app, and that agent communicates out-of-band with a central server monitoring app. If you rely on MQ as the comm transport and MQ has problems, e.g. channel, outage, etc., then you can't relay any meaningful status back to the central monitor. I suppose it all depends on how far you want to take it before you realize it might be more cost effective to buy a solution. Miller, Dennis [EMAIL PROTECTED] OMTo Sent by: MQSeries [EMAIL PROTECTED] List cc [EMAIL PROTECTED] n.AC.AT Subject Re: Connecting to more than one queue managers on solaris, linux 08/31/2004 08:13 PM Please respond to MQSeries List [EMAIL PROTECTED] n.AC.AT I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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
Re: Connecting to more than one queue managers on solaris, linux
Thanks Dennis, I am talking about the agent process, which, by the way, has to monitor some other things on the box than MQ at the same time.. I just do not see any reason for running several such agents just because the box has multiple queue managers on it. If we went for several agents, the administration would get significantly more complicated (in fact, the solution we are currently working with is to open and close connection every time we need a data sample from a particular queue manager. Hopefully this won't kill the box.. this far this hasn't) I do not exactly understand your concerns about the app on one server with mqm credentials for other servers. Doesn't any MQ Server Application with mqm credentials have an access to all queue managers on the box? And doesn't any application need mqm authority to perform, for example, PING CHANNEL with PCF command? Our monitoring application has to be trusted -- that's one reason why I do not want to create a channel for it (with mqm credentials) so that someone could try to impersonate it from the network or another account on the same box. Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 08:13 PM Please respond to MQSeries List I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List
Re: Connecting to more than one queue managers on solaris, linux
The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave
Re: Connecting to more than one queue managers on solaris, linux
Well, for a loopback interface (I mean, when client connects to localhost or 127.0.0.1), it should not call real network drivers. I think it uses some platform-specific IPCs (on solaris, probably streams -- I believe both pipes and local sockets use same underlying mechanisms, on very old Unices it were mbufs) -- and should not be really heavy... Although, the latency will increase due to the agent and some overhead will still be there.. Even when real IP is used, smart TCP stack must not hit the network for local connections. Just thinking aloud.. I have never really tested it with MQ but I did some performance testing with locally bound TCP sockets -- as long as all socket options were set right (especially TCP_NDELAY), the overhead became negligible. Hopefully, IBM got it right :-). Just my 2c Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 09/01/2004 02:39 PM Please respond to MQSeries List The client connection has a performance disadvantage, mostly because of network overhead. After all, every API request (and any messages it conveys) must pass over the network to get between the MQ client and the qmgr. The server channel agent, acting on behalf of the client, uses local bindings and should experience about the same performance as the application using local bindings. But the exchange of API requests between the MQ client and the server channel agent is extra work. I am not in a position to quantify it, though, and I expect it would depend greatly on your network configuration. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 12:48 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux What would the performance difference of using MQClient connections to connect to a local Queue manager on the same Unix host, compared to using a local bindings direct connection to the local Queue manager. I understand that for Pavel's situation, this be be irrelevant, but I am concerned with the general case? Matt. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Miller, Dennis Sent: 01 September 2004 01:13 To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT
Connecting to more than one queue managers on solaris, linux
Hello all, Is there any way to write a C or C++ Server application (multi-threaded, anyway) that talks to more than one queue manager at the same time (meaning -- keeps open more than 1 connection handles, each to its own queue manager)? I need it on Solaris, Linux and possibly AIX. Documentation says no (http://publibfp.boulder.ibm.com/epubs/html/csqzal09/csqzal091w.htm#HDRCONSCP, 4th paragraph from the bottom) -- but I still hope it may somehow be obsolete information :-). I only need it on MQ 5.3. Anyone tried to overcome this before? How do they monitor multiple QMs on Unix these days? If we use clients, can they be secured without using SSL somehow by just using the fact we only need to connect from the local host? Thank you, Pavel -- 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
Re: Connecting to more than one queue managers on solaris, linux
Pavel, A simple exit on the server connection channel can validate from where the connection is coming from ( localhost) and provide the security, if this is all that you are looking for. Raj Pavel Tolkachev [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 08/31/2004 11:43 AM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject:Connecting to more than one queue managers on solaris, linux Hello all, Is there any way to write a C or C++ Server application (multi-threaded, anyway) that talks to more than one queue manager at the same time (meaning -- keeps open more than 1 connection handles, each to its own queue manager)? I need it on Solaris, Linux and possibly AIX. Documentation says no (http://publibfp.boulder.ibm.com/epubs/html/csqzal09/csqzal091w.htm#HDRCONSCP, 4th paragraph from the bottom) -- but I still hope it may somehow be obsolete information :-). I only need it on MQ 5.3. Anyone tried to overcome this before? How do they monitor multiple QMs on Unix these days? If we use clients, can they be secured without using SSL somehow by just using the fact we only need to connect from the local host? Thank you, Pavel -- 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 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: Connecting to more than one queue managers on solaris, linux
Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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: Connecting to more than one queue managers on solaris, linux
Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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
Re: Connecting to more than one queue managers on solaris, linux
Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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 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: Connecting to more than one queue managers on solaris, linux
I have never seen the real reason why a BINDINGS connection has this limitation. Can someone from level 3/2 please explain a single application instance cannot connect to multiple QMs in his scenario? Thanks in advance. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Pavel Tolkachev Sent: Tuesday, August 31, 2004 3:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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 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 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: Connecting to more than one queue managers on solaris, linux
Just as a pure FYI, and I would recommend that anyone act on this, but at various CSD levels for MQ v5 and V5.1, solaris threaded apps COULD connect to multiple queue managers, even though it was officially not a feature. This not-a-feature seemed to come and go a couple of different times, and I don't know what the current state of it is. As you already know, the only supported platform for this feature is windows, otherwise you need to either use client connections or do sub-processes. -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Pavel Tolkachev Sent: Tuesday, August 31, 2004 3:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] Wien.AC.AT OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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 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 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: Connecting to more than one queue managers on solaris, linux
I'm sorry for the typo, but the phrase and I would recommend, should most definitely have been and I would NOT recommend. -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: Kelly F. Hickel Sent: Tuesday, August 31, 2004 3:48 PM To: 'MQSeries List' Subject: RE: Re: Connecting to more than one queue managers on solaris, linux Just as a pure FYI, and I would recommend that anyone act on this, but at various CSD levels for MQ v5 and V5.1, solaris threaded apps COULD connect to multiple queue managers, even though it was officially not a feature. This not-a-feature seemed to come and go a couple of different times, and I don't know what the current state of it is. As you already know, the only supported platform for this feature is windows, otherwise you need to either use client connections or do sub- processes. -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Pavel Tolkachev Sent: Tuesday, August 31, 2004 3:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] Wien.AC.AT OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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 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
Re: Connecting to more than one queue managers on solaris, linux
Thanks Kelly, It is quite clear now.. will consider all options and make my decision.. Pavel Kelly F. Hickel [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:57 PM Please respond to MQSeries List I'm sorry for the typo, but the phrase and I would recommend, should most definitely have been and I would NOT recommend. -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: Kelly F. Hickel Sent: Tuesday, August 31, 2004 3:48 PM To: 'MQSeries List' Subject: RE: Re: Connecting to more than one queue managers on solaris, linux Just as a pure FYI, and I would recommend that anyone act on this, but at various CSD levels for MQ v5 and V5.1, solaris threaded apps COULD connect to multiple queue managers, even though it was officially not a feature. This not-a-feature seemed to come and go a couple of different times, and I don't know what the current state of it is. As you already know, the only supported platform for this feature is windows, otherwise you need to either use client connections or do sub- processes. -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Pavel Tolkachev Sent: Tuesday, August 31, 2004 3:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] Wien.AC.AT OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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
Re: Connecting to more than one queue managers on solaris, linux
I understand your hesitance to use MQ client for such an app. But think about what you are really asking. An app on one server with MQM credentials for other servers? An app on one server with access to MQM internals on another server? Hmmm... I'm sure you know that without MQ-Client, you cannot even connect to a single QMgr across servers, much less multitudes of them. So, if your thinking about monitoring even one qmgr by an app running on a different system, you are talking about some sort of client model, by definition. But it needn't necessarily be the MQ client. You could for example, write a monitoring agent and run it locally on each qmgr. The user interface for your monitoring app is then a client to these agents, requesting services and receiving replies from them. If you are so-inclined, you can even conduct the request/reply exchanges using local connections and MQ messages (although, depending on what you are doing, one might question the wisdom of running a monitoring application in-band like that). It is somewhat analagous to how the command server works, only customized to your specific requirements. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks Dennis, This is a low-level monitoring application (requiring mqm credentials, by the way). Making it an MQ client makes running listener or configured a pre-requisite to operate the app even if there is no business purpose for them to be there and creates a whole number of security issues with the too-far-going implications of their possible solutions. I will have to either live with these consequences or go for running several instances of the app instead (which is not ideal for my cause, either..). Pavel Miller, Dennis [EMAIL PROTECTED]To: [EMAIL PROTECTED] OM cc: Sent by: MQSeriesSubject: Re: Connecting to more than one queue managers on solaris, linux List [EMAIL PROTECTED] n.AC.AT 08/31/2004 04:05 PM Please respond to MQSeries List Yes, you can do it in the server app. Just use the MQ client. A server app from the perspective of the application architecture can be a client from the perspective of MQ. -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 31, 2004 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to more than one queue managers on solaris, linux Thanks David, Is there absolutely no way to do it in the Server app? What is so different between Windows and Unix that you can do it on one but not the other? Thanks, Pavel David C. PartridgeTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIMEUR.COM Subject: Re: Connecting to more than one queue managers on solaris, linux Sent by: MQSeries List [EMAIL PROTECTED] .AC.AT 08/31/2004 11:58 AM Please respond to MQSeries List Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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 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
