| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| QMgr generic name in java & jms |
« View previous topic :: View next topic » |
| Author |
Message
|
| vilyin |
 Posted: Tue Dec 09, 2003 6:29 am Post subject: QMgr generic name in java & jms |
 |
|
Novice
Joined: 26 Mar 2002
Posts: 20
Location: Ilyin Consulting Knowledge, Inc. USA - Boston, NY tri-state
|
Hi all:
This question is to java world people who played with MQ a little:
Is there any way to specify a generic QMgr name for java and jms client? I tried both asterisk(*) and '<partial name>*' w/o success. Is there some sort of escape charecter to use?
Theoretically it should be working following the thought that jms is implemented on top of MQ java classes and java classes in turn implemented on top of C MQI and it does work with C. Both jms and java clients have exactly the same information connecting to the QMgr as their counterparts C clients: server name(ip), port, SVRCONN channel name and QMgr name.
Waiting for suggestions,
Thanks. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Dec 09, 2003 7:00 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I believe the '*' is something that comes into play with the client connection table which is not supported by the Java/JMS. |
|
| Back to top |
|
|
| vilyin |
| Posted: Tue Dec 09, 2003 8:48 am Post subject: |
|
|
Novice
Joined: 26 Mar 2002
Posts: 20
Location: Ilyin Consulting Knowledge, Inc. USA - Boston, NY tri-state
|
Well, it's not only for the clnt table. It's a for any C client.
If you set MQSERVER and connect to the QMgr by specifying its name as star(*) it'll work, even using amqs(put/get)c samples.
And this is very reasonable: you already have specified all the values to establish this connection unambiguously. Whether it's inetd or runmqlsr on the other side, it's listening on a particular port "pointing" to the particular QMgr.
Having being able to specify * as a QMgr name would allow to implement load balancing of the clients at the DNS level oppose to the client side. |
|
| 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
|
|
|
|
