ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Unable to MQ commit (CompCode=2, Reason=2018)

Post new topic  Reply to topic
 Unable to MQ commit (CompCode=2, Reason=2018) « View previous topic :: View next topic » 
Author Message
vj121982
PostPosted: Sun Aug 19, 2007 9:45 pm    Post subject: Unable to MQ commit (CompCode=2, Reason=2018) Reply with quote

Newbie

Joined: 06 Aug 2007
Posts: 5

Hi,
I have a client application putting message in the remote queue, there is no issues with the QueueManager but in between...there are error seen in the logs of the clent application saying that
Unable to MQ commit (CompCode=2, Reason=2018)
this error is seen rarely but its re-occuring.
As far as my knowledege as I went through IBM site to see the reason it says that there is some MQCONN network issue not exactly a MQ error, but I want to know what can be done to fix this issue.


I have HP_UX 11.1 OS and MQ 5.3.

Can someone help on this it will be of great

Thanks
vj129182
Back to top
View user's profile Send private message
Vitor
PostPosted: Sun Aug 19, 2007 11:19 pm    Post subject: Re: Unable to MQ commit (CompCode=2, Reason=2018) Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

vj121982 wrote:
As far as my knowledege as I went through IBM site to see the reason it says that there is some MQCONN network issue not exactly a MQ error, but I want to know what can be done to fix this issue.


According to the IBM site:

Quote:
MQRC_HCONN_ERROR
Explanation:
The connection handle Hconn is not valid, for one of the following reasons:

- The parameter pointer is not valid, or (for the MQCONN or MQCONNX call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
- The value specified was not returned by a preceding MQCONN or MQCONNX call.
- The value specified has been made invalid by a preceding MQDISC call.
- The handle is a shared handle that has been made invalid by another thread issuing the MQDISC call.
- The handle is a shared handle that is being used on the MQBEGIN call (only nonshared handles are valid on MQBEGIN).
- The handle is a nonshared handle that is being used a thread that did not create the handle.
- The call was issued in the MTS environment in a situation where the handle is not valid (for example, passing the handle between processes or packages; note that passing the handle between library packages is supported).
Completion Code:
MQCC_FAILED

Programmer Response:
Ensure that a successful MQCONN or MQCONNX call is performed for the queue manager, and that an MQDISC call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQCONN in the WebSphere MQ Application Programming Guide).


So not so much a network issue as a programming bug, where the handle being used for the commit has gone out of scope or otherwise been rendered useless as indicated above.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
vj121982
PostPosted: Mon Aug 20, 2007 12:41 am    Post subject: Thanks Reply with quote

Newbie

Joined: 06 Aug 2007
Posts: 5

Hi Vitor,
I am very new to MQ hardly 2 months, can you suggest me exactly how can I rectify it,that will of great help.

Thanks
vj121982
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Aug 20, 2007 12:44 am    Post subject: Re: Thanks Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

vj121982 wrote:
I am very new to MQ hardly 2 months, can you suggest me exactly how can I rectify it,that will of great help.


Vitor wrote:
Programmer Response:
Ensure that a successful MQCONN or MQCONNX call is performed for the queue manager, and that an MQDISC call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQCONN in the WebSphere MQ Application Programming Guide).


Don't think I can put it better than that.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
vj121982
PostPosted: Mon Aug 20, 2007 12:47 am    Post subject: Thanks Again Reply with quote

Newbie

Joined: 06 Aug 2007
Posts: 5

Thanks Vitor, I will work on it to see wether I can resolve it.

Regards
vj121982
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Unable to MQ commit (CompCode=2, Reason=2018)
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.