| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Mirrorq Not Mirroring Remote and Client Connections |
« View previous topic :: View next topic » |
| Author |
Message
|
| E. A. Cooke |
 Posted: Mon Apr 09, 2007 9:01 am Post subject: Mirrorq Not Mirroring Remote and Client Connections |
 |
|
Newbie
Joined: 05 Dec 2005
Posts: 8
|
I've read the posts where changing the open options to set all context has cured this and I added it to the open so it reads "O_options = MQOO_OUTPUT | MQOO_FAIL_IF_QUIESCING | MQOO_SET_ALL_CONTEXT;", recomplied, stopped the broker, config mgr and MQS, replaced the exit and restarted and I'm still not getting mirrors of messages coming from another Qmgr or the R/3 Link. Is there anything more to this fix than that? Has anyone else expereinced this?
I've also noticed that when I change the name list I also need to stop and restart the flows in the broker associated with the queues being mirrored or the change is not recognized. Has anyone encountered this with the broker?
My environment is MQS 5.3 CSD 9, WBI/MB 6.0, HP-UX B.11.11. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 09, 2007 11:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The author had a version that fixed this problem, but it seems this fix never quite got distributed before the author was no longer able to support this.
I believe that the fix had something to do with checking the originator of the API connection - whether the message was being put by an MQ program or a customer program( something about "internal" versus "external").
At one point I had a compiled version for AIX, but I don't believe I ever had the corrected source, sorry. Hopefully my poor memory is of some help.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| E. A. Cooke |
| Posted: Thu Apr 12, 2007 8:56 am Post subject: Thanks |
|
|
Newbie
Joined: 05 Dec 2005
Posts: 8
|
Jeff,
Thanks for responding. I did see that post, but as you said, there was no code posted at that time that I could see. It just refered to the problem having to deal with internal connections. I did notice that the source refers to the MQ_CONNX_EXIT for both Conn and Connx. I'll look deeper into that area. |
|
| 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
|
|
|
|
