| Author |
Message
|
| mdncan |
 Posted: Wed Apr 09, 2008 4:53 am Post subject: Inactivate Server Connection Channel after client discont |
 |
|
Acolyte
Joined: 11 May 2005
Posts: 59
Location: US
|
Hi All,
I am having a strange behaviour on a Server Connection Channel: Even after client connections stopped/terminated, I still see active connections on the Server Conn channel.
What could be the reason for these connections to be still there? For now I am manually stopping the Server Conn Channel and bringing up my the Application. I would like to know if there is any tuning that I can do on the Server Conn to close the orphaned client connections.
Thanks in advance!!!
Regards,
_________________
IBM Certified System Administrator- WebSphere Application Server, Network Deployment, V6.0
IBM Certified System Administrator - WebSphere MQ V6.0 |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Apr 09, 2008 4:56 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What else, apart from the clients you expect, might be attaching?
_________________
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. |
|
| Back to top |
|
|
| mdncan |
| Posted: Wed Apr 09, 2008 4:59 am Post subject: |
|
|
Acolyte
Joined: 11 May 2005
Posts: 59
Location: US
|
None, this Server Conn is purely for Client Connections from the App.
I have different Server Conn's for other purposes viz., remote admin.
Thanks |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Apr 09, 2008 5:02 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Search for 2009 / connection broken in this forum,
you will lots of results.... 
you can tune the same.
 Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Apr 09, 2008 5:02 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| You mention the client apps are stopping/terminating; however you don't say whether ot not they are properly disconnecting. I would wager a guess that they're not doing a proper MQDISC and you are getting some orphaned connections. |
|
| Back to top |
|
|
| gs |
| Posted: Wed Apr 09, 2008 5:22 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
| A hint is to look for TCPKeepAlive. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Apr 09, 2008 5:23 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| gs wrote: |
| A hint is to look for TCPKeepAlive. |
While that may help to clear up the orphaned connections, it does not explain the cause of them. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Apr 09, 2008 5:32 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| Toronto_MQ wrote: |
| gs wrote: |
| A hint is to look for TCPKeepAlive. |
While that may help to clear up the orphaned connections, it does not explain the cause of them. |
But inorder to wipe off, TCPKeepAlive is the best option.
Cause could be App is not disconnecting properly, and OS Depend too
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mdncan |
| Posted: Wed Apr 09, 2008 5:49 am Post subject: |
|
|
Acolyte
Joined: 11 May 2005
Posts: 59
Location: US
|
Thanks for your replies.
- the client application is a vendor .NET application, so I don't have any clue how they are handling the disconnects/close (No help from the vendor, people @vendor I speak don't have proper MQ knowledge )
- current KeepAlive is set to "AUTO" - should I change to the value "0"?
- As some of you mentioned, Yes I am looking to find a root cause of the issue.
Thanks,
_________________
IBM Certified System Administrator- WebSphere Application Server, Network Deployment, V6.0
IBM Certified System Administrator - WebSphere MQ V6.0 |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Apr 09, 2008 6:11 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
KeepAlive is set to "YES"
Request you to search, learn, understand first  
(WHAT, WHY, WHEN, HOW , regarding this)
Then think of applying it.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Apr 09, 2008 8:01 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| mdncan wrote: |
- the client application is a vendor .NET application, so I don't have any clue how they are handling the disconnects/close (No help from the vendor, people @vendor I speak don't have proper MQ knowledge )
|
Then I think there is a good chance you have found your problem. Open a problem ticket with the vendor, if such a route exists. It is likely they are not properly disconnecting.
I've seen it FAR too many times.
Steve |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Apr 09, 2008 10:20 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Maybe the app is using connection pools. The app "disconnects" but all that does is return the hConn to the client side connection pool. At that point its still a valid connection to the QM. TCP Keep Alive will do nothing in this case. They are valid channels and TCP Keep Alive doesn't kill valid channels, no matter how old they are.
If the app is truly ended, and there are ZERO executables left behind that might be maintaining a pool, then I would be very suprised for .NET. I tried to force this to happen in my app to test stuff. I purposly skipped MQCLOSE and MQDISC when ending. But apparently there is some garbage collection built into the .NET MQ dll that cleaned up. Even when I ended my apps exe in Task Manager it still cleaned up the channels. The only way I was able to cause my VB.NET app to leave behind an orphaned connection was to yank the network cable from the back of my laptop.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
