| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC_CONNECTION_BROKEN upon disconnect |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ron.Benchetrit |
 Posted: Tue Feb 13, 2007 1:17 pm Post subject: MQRC_CONNECTION_BROKEN upon disconnect |
 |
|
Newbie
Joined: 13 Feb 2007
Posts: 2
Location: New York City
|
Client: MQ 5.3 w/.NET using SSL on Win2003 svr
Server: MQ 6.0.1 on SUSE 9.1
Hello all,
We have a .NET client running as a NT service which makes four MQ connections from two threads. The service runs great all day processing almost 10,000 messages. It then goes basically unused (no messages) after workhours until about 11pm when the threads are shutdown to do some house keeping. Upon disconnecting, we get MQRC_CONNECTION_BROKEN. After housekeeping is done, the threads startup and reconnect quite happily as if nothing was ever wrong.
In my test and dev environments, I've never seen this error. Only when we went live in production did this error suddenly appear, consistently every nightly.
Something else I noticed is that I only see two connections on the production channel whereas I would expect to see four as I do in dev and test.
Any ideas?
Thanks,
Ron Benchetrit
Software Development Manager |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Feb 13, 2007 3:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Firewall timeout maybe ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Ron.Benchetrit |
| Posted: Wed Feb 14, 2007 6:30 am Post subject: |
|
|
Newbie
Joined: 13 Feb 2007
Posts: 2
Location: New York City
|
Yup, upon further investigation, I'm convinced that one of the 4 hops between the server and client is dropping the connections. Not a firewall, but possibly a NAT router or and overly protective router. They drop exaclty 60 minutes after last use.
I've determined that it's my request queues which die out because they go completly unused. By reply queues are fine because I am constanly polling them with a check of their queue depth.
So the new question is how to keep an inactive request queue alive? I'm somewhat familiar with mq.ini keepalive. But how about a client side solution?
Ron
_________________
Ron Benchetrit
Software Development Technical Manager |
|
| Back to top |
|
|
| Jmeek |
| Posted: Wed Feb 21, 2007 12:02 pm Post subject: |
|
|
Novice
Joined: 19 Dec 2005
Posts: 10
Location: Winston Salem, NC
|
Did you ever find a solution to this problem? I am having a simular situation between 2 seemingly identical systems.
Quick rundown:
MQv5.3 CSD13
AIX v5.2
SVRCONN channel idle for exactly 60 minutes is disconnected. Application receives Reason Code 2009, but nothing in the MQ QMgr error log at the time the connection was dropped.
The real problem is that I can't duplicate it on our test server and it is happening in Prod.
Any help?
Thanks in advance. 
_________________
All else fails, RTFM. |
|
| 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
|
|
|
|
