| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| C++ API : put fails despite remote named queue is opened |
« View previous topic :: View next topic » |
| Author |
Message
|
| alexdk92 |
 Posted: Wed Jul 24, 2013 7:29 am Post subject: C++ API : put fails despite remote named queue is opened |
 |
|
Newbie
Joined: 24 Jul 2013
Posts: 2
|
Hello All,
I am using MQ C++ API to put messages onto remote named queue. My main reference is MQ C++ manual HTMLs and sample programs.
I can successfully open the queue (I also did tcpdump/wireshark capture and I see good MQOPEN_REPLY message from the remote Queue Manager with good object and options in it).
However, ImqQueue::put(msg) on the object that has just been successfully opened fails with reason code 2018 (invalid connection handle) and I am pretty much stuck in trying to find out what's wrong.
I am using default put message options.
Queue open options are MQOO_OUTPUT + MQOO_INQUIRE + MQOO_FAIL_IF_QUIESCING , and are validated with openFor() call.
There is nothing in /var/mqm/errors or /var/mqm/log.
Any advice on how to further drill down to the cause of this problem would be highly appreciated. E.g. some MQ API trace, or activation of detailed logging ? Any additional manual chapter that I need to read on top of MQ C++ API documentation ?
Thanks in advance,
Alex |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 24, 2013 7:39 am Post subject: Re: C++ API : put fails despite remote named queue is opened |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| alexdk92 wrote: |
| However, ImqQueue::put(msg) on the object that has just been successfully opened fails with reason code 2018 (invalid connection handle) and I am pretty much stuck in trying to find out what's wrong. |
Is the original connection to the queue manager a shared or non-shared handle? If it's non-shared, is it in a different thread to the one doing the put? If it's shared, has a different thread disconnected?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| alexdk92 |
| Posted: Wed Jul 24, 2013 8:32 am Post subject: |
|
|
Newbie
Joined: 24 Jul 2013
Posts: 2
|
Thanks for your brilliant response.
Indeed I was opening the queue in a thread other than the one calling put() and queue manager handle had no sharing options set.
I should have indeed taken more time to read the page explaining reason code 2018  
Problem solved now! |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 24, 2013 9:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| alexdk92 wrote: |
| Thanks for your brilliant response. |
You're welcome
| alexdk92 wrote: |
| I should have indeed taken more time to read the page explaining reason code 2018 |
Never underestimate the depth of the IBM documentation.
| alexdk92 wrote: |
| Problem solved now! |
Well done you! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
