| Author |
Message
|
| MQChela |
 Posted: Mon Jul 09, 2012 11:46 am Post subject: Client connection mode to queue manager on same server |
 |
|
Novice
Joined: 07 Feb 2006
Posts: 20
|
Hi,
I assume connection will use network when using client connection mode (instead of binding mode) to access queue manager on same server.
Can someone please confirm this?
And is it true that Solaris OS is smart to detect that an application is attempting to connect to local queue manager and hence will not connect via network?
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jul 09, 2012 11:56 am Post subject: Re: Client connection mode to queue manager on same server |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQChela wrote: |
| I assume connection will use network when using client connection mode (instead of binding mode) to access queue manager on same server. |
Yes
| MQChela wrote: |
| And is it true that Solaris OS is smart to detect that an application is attempting to connect to local queue manager and hence will not connect via network? |
No.
The client connection always runs via the "network", but if the connection is to the local box most TCP/IP software (including that employed by Solaris) doesn't bother to push the packets out of the hardware over the wire to bounce off some hardware network component because the address resolution will prevent it.
So you don't (even of Solaris) automagically get a binding connection if you start a client on the queue manager's server. But you do get network traffic that doesn't leave the machine's TCP/IP stack.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jul 09, 2012 11:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You need to ask your Solaris administrator how it will route traffic to the ip address/hostname that you are told to use.
Most OSes will intentionally shortcut anything routed to localhost. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 09, 2012 11:57 am Post subject: Re: Client connection mode to queue manager on same server |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQChela wrote: |
| I assume connection will use network when using client connection mode (instead of binding mode) to access queue manager on same server. |
Yes
| MQChela wrote: |
| And is it true that Solaris OS is smart to detect that an application is attempting to connect to local queue manager and hence will not connect via network? |
No.
The client connection always runs via the "network", but if the connection is to the local box most TCP/IP software (including that employed by Solaris) doesn't bother to push the packets out of the hardware over the wire to bounce off some hardware network component because the address resolution will prevent it.
So you don't (even of Solaris) automagically get a binding connection if you start a client on the queue manager's server. But you do get network traffic that doesn't leave the machine's TCP/IP stack.
Also, and for the record, Solaris doesn't know any more than any other OS knows that you're trying to connect to a local queue manager. All it can see is TCP/IP traffic that's addressed locally. It doesn't know about queue managers, or much care either way.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQChela |
| Posted: Mon Jul 09, 2012 12:00 pm Post subject: Thanks |
|
|
Novice
Joined: 07 Feb 2006
Posts: 20
|
Thanks for quick replies
 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 09, 2012 1:17 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
A bit more of an explanation:
Your bound (link-edited) executable contains your compiled C (or COBOL or...) object code, AND WMQ code. The WMQ code determines how the connection will take place. The WMQ code comes in two flavors: client- and server-bindings.
Server-bindingsWMQ software will connect to the qmgr via o/s cross-memory services. This means across virtual storage (effectively RAM); and no network flows will take place. The server-bindings app must execute in the same o/s image as the qmgr.
Client-bindings WMQ software will connect to the qmgr across a traditional network. Your client-bindings app may or may not execute in the same o/s image as the qmgr.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
