| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CLNTCONN channel accessing multi-instance Qmgr possible? |
« View previous topic :: View next topic » |
| Author |
Message
|
| pcelari |
 Posted: Fri May 04, 2012 9:56 am Post subject: CLNTCONN channel accessing multi-instance Qmgr possible? |
 |
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
Hello,
the MQ document is a little vague about accessing multi-instance qmgr.
on document fa70155_:
"The CONNAME attribute of channels is a comma-separated list of connection names; for example, CONNAME('92.46.1.1(1415), 85.42.3.8(2423)'). The connections are tried in the order specified in the connection list until a connection is successfully established. If no connection is successful, the channel attempts to reconnect."
It is not clear if this statement also applies to client connection channel definition. I tried this in my clntconn channel by copying the channel table to a Windows PC with MQ client v7.0.1.6. The connection to the first one works fine when the first instance is active; but after fail-over to the second instance on a different server, the connection didn't work.
When I run the saveqmgrc command from a Windows PC got this below:
With no client connection information specified.
MQCONNX failed for QMGR, CC=2 RC=2538
here's the CONNAME field in the definition of my clntconn channel:
def chl(MYQM.CLNTCONN) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
qmname(MYQM) CONNAME(server_p(1417), server_s(1417))
Can anyono more knowledgeable provide a clearer statement on this subject?
thanks a lot!
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri May 04, 2012 11:02 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
Did you research RC=2538?
_________________
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 |
|
|
| pcelari |
| Posted: Mon May 07, 2012 7:54 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
of course, that's the first thing I did:
"2538 0x000009ea MQRC_HOST_NOT_AVAILABLE".
but the host server_s(1417) is available, with listener running.
thanks,
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 07, 2012 8:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| pcelari wrote: |
of course, that's the first thing I did:
"2538 0x000009ea MQRC_HOST_NOT_AVAILABLE".
but the host server_s(1417) is available, with listener running.
thanks, |
I believe this RC is more common in SSL scenarios...
and it's meaning is closer to SSL misconfigured...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| issac |
| Posted: Tue May 08, 2012 11:51 pm Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello,
have tried ping server_p on your client's machine ?
CLNTCONN supports mi qmgrs for sure.
_________________
Bazinga! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
