| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC_ANOTHER_Q_MGR_CONNECTED |
« View previous topic :: View next topic » |
| Author |
Message
|
| vmcgloin |
 Posted: Mon Nov 18, 2002 7:14 am Post subject: MQRC_ANOTHER_Q_MGR_CONNECTED |
 |
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Does it make sense to make an MQ server connection to a qmgr AND an MQ client connection to another qmgr in the same process?
We have written an MQ interface for a 3rd party application. It turns out that this application, over which we have no control, already has an MQCONNection to qmgr A, presumably in the same process. We want our interface to connect to qmgr B.
Initially we were getting: MQRC_ANOTHER_Q_MGR_CONNECTED
and decided to compile the interface with the client libraries so that we could connect to another qmgr. This seems to work using a test harness.
However, using the interface (an AIX shared object) with the 3rd party app still produces MQRC_ANOTHER_Q_MGR_CONNECTED (2103).
Any suggestions welcome! |
|
| Back to top |
|
 |
| bduncan |
| Posted: Mon Nov 18, 2002 11:09 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
I think you need to ask yourself if there is any way to leverage the already existing MQSeries connection, removing the need for a second connection. Perhaps qmgr A can act as a proxy for qmgr B, rather than trying to connect to B directly? If not, perhaps you can fork the process? Multiple threads should be able to make individual queue manager connections. But unfortunately, a single thread cannot make more than one MQSeries connection at a time.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| 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
|
|
|
|
