|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Occationally getting error RC 2009 CONNECTION BROKEN |
« View previous topic :: View next topic » |
Author |
Message
|
swami_sarvesh |
Posted: Tue Jun 24, 2014 6:10 am Post subject: Occationally getting error RC 2009 CONNECTION BROKEN |
|
|
Newbie
Joined: 24 Jun 2014 Posts: 1
|
Hello,
While reading message from WMQ, theconnection between server and client getting broaken occationally. I am using Informatica tool to read the MQ messages. Informatica in turn built in C. The Client is MQ 7.0.1.0 for solaris-sparc and server is MQ 6.0.0 on solaris.
At the client side it is generating .FDC file. The FDC file says as Protocol error.
Probe Id :- RM496003
Probe Type : MSGAMQ9504
Component :- reqMakeCall
SCCS Info :- lib/cs/amqxeida.c, 1.106
Line Number :- 4834
Build Date :- Aug 13 2009
Major Errorcode :- rrcE_PROTOCOL_ERROR
At the server end it is logging following error:
----- amqccita.c : 3094 -------------------------------------------------------
06/08/14 19:59:54 - Process(8222.121500) User(mqm) Program(amqrmppa)
AMQ9209: Connection to host 'wpsun320 (10.52.3.52)' closed.
EXPLANATION:
An error occurred receiving data from 'wpsun320 (10.52.3.52)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
Please note that, this doesnot happen for all the messages. Some times it happenss. Once this error happens contineously happen. In such case, we are using some other tool to cleanup the messages. After that again it processes successfully.
Please let me know how to resolve this issue.
Thanks in advance. |
|
Back to top |
|
 |
zpat |
Posted: Tue Jun 24, 2014 6:20 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Apply the fixpacks - you should never be using the first version of a release years later!
v7.0.1.11 is the current version (of 701) (you can fixpack it or just install the client built at that level).
As for a v6.0.0 queue manager - you are surely joking. It's been out of support for years now, and that version must be about 10 years old?
Absolutely no point trying to diagnose the issue on truly ancient versions.
If you are going to upgrade, you may as well go to v7.5.0.3 _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Jun 24, 2014 9:20 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Fix Pack 12 has been out for 7.0.1 for a couple of months now. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
gbaddeley |
Posted: Tue Jun 24, 2014 4:38 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
It could be an issue with the TCP stack on the client or server systems or an issue with the network, such as dropped packets.
In any case, upgrade to supported MQ versions and the latest FixPacks. _________________ Glenn |
|
Back to top |
|
 |
JosephGramig |
Posted: Wed Jun 25, 2014 12:04 pm Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
And search this forum for "stanzas" and you will find good info. |
|
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
|
|
|
|