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 » MQ Connections not timing-out

Post new topic  Reply to topic
 MQ Connections not timing-out « View previous topic :: View next topic » 
Author Message
rposey
PostPosted: Wed Dec 05, 2001 1:51 pm    Post subject: Reply with quote

Newbie

Joined: 06 Jun 2001
Posts: 2
Location: DotsConnect

The Server Connection Channel is still showing connections held from a Client even after the Client has, stopped all services to the MQ Server, Shutdown the Client PC and unplugged from the Network. This causes several problems. For one MQ on NT/2000 can have 100 connections per port (1414). When the client disconnects and reconnects several time during the day the connections build up and max out the Server Connection Channels connection limit.

Is anyone aware of any patches/solutions for this type of issue?

Product: MQSeries 5.2
CSD level: CSD01
OS: Windows 2000 SP2
Hardware: Compaq DL380 W/dual 733mhz and 512 RAM

Server
Running a NETSTAT -an from the command line on the MQ server shows multiple sessions open from the Client.

Client
Running a NETSTAT -an from the command line on the Client PC shows no connections to the MQ Server.

If anyone out there has experienced a similar issue on this type of Platform, I am in need of a solution.

Back to top
View user's profile Send private message Visit poster's website AIM Address
PeterPotkay
PostPosted: Thu Dec 06, 2001 10:52 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7717

Double check that the application specifically MQCLOSEs the queue and MQDISCs from the Queue Manager. We had an app that simple ended when it was done, and since it didn't close the queue or disconnect, it kept leaving these orphaned connections. we had the coder add the 2 calls and the problem went away.

_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
StefanSievert
PostPosted: Thu Dec 06, 2001 5:03 pm    Post subject: Reply with quote

Partisan

Joined: 28 Oct 2001
Posts: 333
Location: San Francisco

Hi,
in addition to a well behaved application, proper setting of the TCP/IP KeepAlive parameters will help with clearing up orphaned server side client channels. This links http://www-4.ibm.com/software/ts/mqseries/support/tandts/keepaliv.html and http://www-4.ibm.com/software/ts/mqseries/support/tandts/heartb.html contain a good description of the related issues.
Searching the Microsoft Knowledge base for TCP/IP KeepAlive will reveal how to modify the registry: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q120642
The MS provided defaults are certainly not very helpful, because a broken client connection will only be detected after about 2 hours.
Let me know, if you need more help and I'll dig in my datasink.
Cheers,
Stefan

_________________
Stefan Sievert
IBM Certified * MQSeries

[ This Message was edited by: StefanSievert on 2001-12-06 17:04 ]

[ This Message was edited by: StefanSievert on 2001-12-06 17:09 ]
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 » MQ Connections not timing-out
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.