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 » 2009 Errors on client (MQRC_CONNECTION_BROKEN)

Post new topic  Reply to topic Goto page Previous  1, 2
 2009 Errors on client (MQRC_CONNECTION_BROKEN) « View previous topic :: View next topic » 
Author Message
PeterPotkay
PostPosted: Tue Apr 13, 2004 5:52 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

If you are using bindings mode, then you are not using channels, so don't bother with those parameters (to solve this problem).

Not an answer to your problem, I know, but at least it will keep you from wasting your efforts on something that is not involved in the situation.


If there are no errors in the logs, and the problem occurs regularly or you can recreate it at will, then maybe its time to start an MQ trace and ship the files off to IBM. But those may not even show anything other than your connection being dropped somehow. But maybe its worth a shot, as it seems you have tried everything else.

You are positive that you are running in bindings mode? If not 1000% sure (just because a developer says they compiled it one way does not mean that is the version you are running) then do a channel status on all your SVRCONNs while the app is running to make sure there are no connections from that box.

These aren't the best answers, but easily done to eliminate possibilitys. Don't know what else to try.

This is a good one if it is in fact bindings mode.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
aboggis
PostPosted: Wed Apr 14, 2004 9:22 am    Post subject: Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

A good call on checking the SVRCONN channel status. However, I had done that to confirm and the only SVRCONN connections that ever show up are me when I use MQExplorer from a Windows environment to connect to one of these Solaris based qmgrs.

I had pretty much come to the trace option too. I just need to get to a point where the error is replicable reliably.

I personally feel it's likely to be an internal application error, but I shall continue to investigate.

Since it always seems to happen on an MQGET (which is also making me think it's an application, not MQ, issue) I will also look into an API exit.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
JasonE
PostPosted: Mon Apr 26, 2004 6:00 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

Obvious question I guess, but have you checked for FDC files as well?
Back to top
View user's profile Send private message
aboggis
PostPosted: Mon Apr 26, 2004 12:19 pm    Post subject: Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

Yes, I did. Nothing helpful there.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
mqonnet
PostPosted: Mon Apr 26, 2004 12:41 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Is this a repeatable scenario. Meaning, can you somehow track this down and make it happen at will. If you are, then it would be easy to nail this one.

Few questions though.

-Whats the app doing.
-Can you post the code.
-Whats the scenario.
-How busy is the system.
-Is the qm up and running even after the app gets a 2009 on mqget api call.
-What happens to other apps that are connected at around the same time this happens.
-You sure you checked the right QM FD files. At times we mistakenly look at the wrong qm for the FD files. Not saying you did that. But double check them. Because a 2009 should generally speaking, write something someplace. FD files or mqerrorlogs.
-Also confirm that you are running this in bindings mode as peter suggested.


Got this from the manuals.

"If the call is an MQGET call with the MQGMO_WAIT option, the wait has been canceled. All connection and object handles are now invalid."

Sure is a pretty odd one, if this is hapenning on the system where the qmgr resides and the app is in bindings mode.

Cheers
Kumar
Back to top
View user's profile Send private message Send e-mail Visit poster's website
JasonE
PostPosted: Tue Apr 27, 2004 6:28 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

If you can recreate it, get a trace - It will indicate what the problem is, although you may need to trace both the client and server side concurrently. If you do get a trace I may be able to take a quick look at it.
Back to top
View user's profile Send private message
aboggis
PostPosted: Tue Apr 27, 2004 9:43 am    Post subject: Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

I am in the process of gathering (or at least trying to gather...) some trace files on this. Funny thing is, we got the failure scenario, stopped the app, started a trace run (with just the -t api option), restarted the app, and of course it didn't fail this time - at least not in the same way!

-What's the app doing: Getting a message from a local queue.
-Can I post the code: Not at the moment, since we have not isolated the error. However I have reviewed several areas of the code where MQGETs are done and at least at a high level (I do come from a development background) I see nothing amiss. Although I won't rule out posting some code at a later date.
-How busy: Not very.
-Is the qm up and running... :Yes. There seems to be no obvious errors on the qm.
-Wrong FDC files: Not likely as this system only hosts a single qmgr.
-We are running in bindings mode. Linked with libmqm.so

Where in the manual was that caveat? I'll look into that. I don't believe the code is specifying a wait - I'll dbl check.

JasonE: As I said, I am trying to generate some traces. I have a bunch of trace files, and am looking into them. Is there any advanced docs on interpreting the formatted trace files (I've run them thru dspmqtrc).
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
JasonE
PostPosted: Wed Apr 28, 2004 12:43 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

No docs, I'm afraid. MQRC 2009 shows
2009 0x000007d9 MQRC_CONNECTION_BROKEN
So grep the traces for 7d9 2009 or CONNECTION_BROKEN for a starting point. I suspect you would only see this error from the client side though, an dneed to work backwards. (In which case a search for exception is a good starting point normally).
(I've sent you an email offline as well.)
Back to top
View user's profile Send private message
JavaGuru
PostPosted: Fri Jan 21, 2005 6:52 am    Post subject: Any progress? Reply with quote

Newbie

Joined: 21 Jan 2005
Posts: 1

I too am experiencing this problem. I am running WebSphere 4.0 on Solaris 5.8 We have MQ 5.3 CSD04 running on a seperate Solaris box. I am getting intermitent 2009 errors on the client with no corresponding errors on the QueueManager. We have extensively experimented with the MAX CHANNELS to no avail. We do not seem to be running out of channels nor do we seem to be experiencing network issues. I was wondering if you made any progress in resolving this issue in your system and might have some advice for us. Thanks a lot.
Back to top
View user's profile Send private message
ashishscindia
PostPosted: Thu Feb 17, 2005 1:21 pm    Post subject: Reason 2009 Reply with quote

Newbie

Joined: 17 Feb 2005
Posts: 1

We have been getting this error for quite some time:

com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009

Environment:

Websphere Studio (WSAD 5.0.1) with embedded JMS installed as a client on my Windows XP machine. The MQ Server is installed on AIX box on the network.

I have tried installing MQ 5.30.x CSD04 on my machine (this is an alternative for embedded JMS) but still get the same Reason 2009 error upon connection.

Possible solutions I tried:
1> Installing different versions of MQ and WSAD without any success.
2> Playing with MQ environment variable.

Well nothing really helps so any help from IBM or MQ expert is required.

Regards,
Ak
Back to top
View user's profile Send private message
csmith28
PostPosted: Thu Feb 17, 2005 1:28 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

Quote:
2009 X’07D9’ MQRC_CONNECTION_BROKEN
Connection to the queue manager has been lost. This can occur because the queue manager has ended.


It can also occur if there is an interruption in network connectivity. In my personal experience this is the more likely scenario.

Quote:
If the call is an MQGET call with the MQGMO_WAIT option, the wait has been
canceled. All connection and object handles are now invalid.
For WebSphere MQ client applications, it is possible that the call did complete successfully,
even though this reason code is returned with a CompCode of MQCC_FAILED.

Corrective action: Applications can attempt to reconnect to the queue manager by issuing the
MQCONN or MQCONNX call. It may be necessary to poll until a successful response is
received.


Quote:
On z/OS for CICS applications, it is not necessary to issue the MQCONN or MQCONNX call,
because CICS applications are connected automatically.
Any uncommitted changes in a unit of work should be backed out. A unit of work that is
coordinated by the queue manager is backed out automatically.


Usually when I see this it means that there was some kind of Network latency between the Remote Client Application Server and the MQManager Server. The application loses it's connection and the code isn't intelligent enough to re-connect to the MQManager.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.


Last edited by csmith28 on Thu Feb 17, 2005 11:10 pm; edited 1 time in total
Back to top
View user's profile Send private message
bower5932
PostPosted: Thu Feb 17, 2005 1:58 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

In my experience, the usual problem for this error when using WSAD is having an old jar file laying around. Make sure that you are picking up your MQ jar files from your 5.3 fixpack 4 code and not something that was delivered through WSAD.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
fjb_saper
PostPosted: Thu Feb 17, 2005 2:23 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

The other usual problem still using WAS is to have the connection pool defined too small. The 2009 may then be dependant on web activity. Very difficult to reproduce.

Enjoy
Back to top
View user's profile Send private message Send e-mail
hotsdogs
PostPosted: Tue Apr 18, 2006 2:01 pm    Post subject: Reply with quote

Newbie

Joined: 15 Nov 2004
Posts: 5

I too am experiencing this problem. I have a machine with MQ, four queue managers. Windows 2000 server. Under on of the queue managers 7 channels and 16 queues. 7 input queue, 7 output queues for our clients to send and receive messages. Two queues for our programs to process the messages and reply. Each input/output queue pair uses its own channel. Out clients connect over the internet using SSL as we have a shareware Security Exit set up to only allow certain users to connect to each channel.

The problem is that about once every two or three weeks we get the following error:
MQRC_CONNECTION_BROKEN, amqmdnet -- at IBM.WMQ.MQQueue.Get(MQMessage message, MQGetMessageOptions gmo, Int32 maxMsgSize)
.
This usually happens during the day after the programs have been running for a while and processing messages with no problems.


Our client programs are written in c# and our Customer's programs are in Delphi I believe.


None of the other Queue managers are effected and their traffic is much higher but their connects are lower, only this queue manager and all programs connected through this Queue manager fail. The traffic is not too heavy. We see nothing in the logs and typically have to reboot the server to get things working again.
Back to top
View user's profile Send private message Send e-mail MSN Messenger
java_ppl
PostPosted: Fri Sep 22, 2006 7:34 am    Post subject: Reply with quote

Novice

Joined: 22 Sep 2006
Posts: 13

Hi ,
I am facing a similar problem. 2009
In my case , I know why its happening : The ClientIdle parameter has been set to a particular time interval.. And after this time the connection is Broken.

The java application I'm working on polls a directory for a file. Once it detects a file, it transfers its contents to a message and puts in on a queue.

So when my application attempts to access the queue after this timeinterval (in other word there has been no activity over this channel for more than ClientIdletime .. , i get the exception : com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
)

My problem is .. i do not know how to make it reconnect.

I have tried two things:
1. Removing MQC.MQOO_FAIL_IF_QUIESCING option while creating the queues
2. in the getMessage function where exception occurs, I've put a while loop :
while(flag)
{
try {
queue.get(message, gmo);
flag=false;
} catch (MQException e)
{
// queueManager.disconnet();
ShutdownHandler shutdownHandler = new ShutdownHandler();
shutdownHandler.run();
MQController.createWMQObjects(Config.getQueueManagerName(), Config.getQueueName());

}

}

return message;

[createWMQObjects() : Create and connect to the WMQ objects required by the gateway
shutdownHandler.run() : Backout any WMQ Units of Work and dereference any WMQ objects ]


Nothing worked.

What I require is : If I place a file in the directory the application polls, after the specified time interval also , it will encounter broken connection , but should reconnect and proceed(transfer file contents to msg) .


Is there any other way i can over come this?

thanks
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » 2009 Errors on client (MQRC_CONNECTION_BROKEN)
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.