MQSeries.net :: View topic - reason '2009' ('MQRC_CONNECTION

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » reason '2009' ('MQRC_CONNECTION_BROKEN').

reason '2009' ('MQRC_CONNECTION_BROKEN').

« View previous topic :: View next topic »

Author

Message

suneel

Posted: Thu Mar 03, 2011 2:34 am Post subject: reason '2009' ('MQRC_CONNECTION_BROKEN').

Voyager

Joined: 06 Nov 2009
Posts: 89

mqjeff

Posted: Thu Mar 03, 2011 4:46 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

That FDC doesn't say anything about the source of the problem.

2009 is either an issue with too many channels being open - perhaps the app is forgetting to close them or is opening and closing them too often - or it's an issue with the network.

Mr Butcher

Posted: Thu Mar 03, 2011 5:01 am Post subject:

Padawan

Joined: 23 May 2005
Posts: 1716

Quote:

Whenever it occurs we had go go for QM bounce

this is very suspicious and i think mqjeff already pointed you into the correct direction to check if some of your ressources are exhausted. what about the amqerrxx.log files? no entries in there?

Quote:

Please provide a permanent solution.

many different issues may pop up with 2009, so i am afraid you need to uninstal for a permanent solution

_________________
Regards, Butcher

gbaddeley

Posted: Thu Mar 03, 2011 5:58 pm Post subject:

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

2009 covers a multitude of possible networking and app process related issues, none of which MQ has control over or can effectively recover. It generally indicates an establish comms session (eg. a TCP/IP Socket) between two Message Channel Agents (I include the MQ Client libraries here) failed unexpectedly. Sometimes there is an errno, winsock or zOS oesocket return code in the MQ logs which may shed some light on the real issue.
_________________
Glenn

santnmq

Posted: Thu Mar 03, 2011 9:19 pm Post subject:

Centurion

Joined: 11 Jan 2011
Posts: 125

connection to the server can be broken beacuse of the several reasons including network issues also. Make sure that at any point in time the total number of client connections are below the specified limit.

Also, if your client connection breaks because of the error in the client program, the connection can not be established again till you restart the client app and the queue manager.

Thoroughly monitor the client connections and see what is the exact cause of this issue.

bruce2359

Posted: Thu Mar 03, 2011 10:00 pm Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Quote:

till you restart the client app and the queue manager.

Really?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.

santnmq

Posted: Fri Mar 04, 2011 3:08 am Post subject:

Centurion

Joined: 11 Jan 2011
Posts: 125

I had faced the similar kind of problem which gets resolved once you restart the client app or the queue manager.

What I could probably makeout from that is, it was necessary in that scenario to first close all the previous connections to get a new successful connection to the server.

It may not be true for all scenarios.

bruce2359

Posted: Fri Mar 04, 2011 6:38 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Quote:

...gets resolved once you restart the client app or the queue manager.

Restarting the qmgr is like rebooting Windoze - it doesn't really fix the underlying cause of the problem, or anything else.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.

suneel

Posted: Tue Mar 08, 2011 1:51 am Post subject:

Voyager

Joined: 06 Nov 2009
Posts: 89

Hi,

Restarting the QM is not a permanent solution. Eventhough Applications are bounced still we are facing the same issue

exerk

Posted: Tue Mar 08, 2011 4:06 am Post subject:

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

suneel wrote:

Restarting the QM is not a permanent solution. Even though Applications are bounced still we are facing the same issue

You can bounce your applications as much as you like but if the problem is at the queue manager end it makes no difference. As has been suggested, check the queue manager error logs for MaxChannels/MaxActiveChannels events.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.

vmcgloin

Posted: Tue Mar 08, 2011 4:50 am Post subject:

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Clearly you need to examine the qmgr logs as already suggested given that restarting the apps does not help. Does it really not help, or it is that the problem occurs again some time later?

Do you use keepalive? Is there something in your network breaking connections? Do you have code in your applications to reconnect cleanly when getting a 2009?

On your FFST (unrelated to the 2009 as has already been stated) you should read http://hursleyonwmq.wordpress.com/2007/05/04/introduction-to-ffsts/ (an old doc I still regularly refer new admin's to).

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » reason '2009' ('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