Author |
Message
|
Volvic |
Posted: Tue May 31, 2011 1:51 am Post subject: Windows 2003 Connection Limit |
|
|
Apprentice
Joined: 14 Oct 2009 Posts: 30
|
Hi all,
I know there is a parameter for WebSphere MQ that I can put into the registry (MaxActiveChannels) for limiting the maximum active channel count but what about TCP/IP connections on a Windows 2003 Server?
What if I want to set MaxActiveChannels to 6000?
Is this possible or will Windows block my connections?
Is one SVRCONN instance = TCP/IP connection? How many SVRCONN instances are ok for a Windows Server?
Is it documented somewhere? _________________ Volvic |
|
Back to top |
|
 |
exerk |
Posted: Tue May 31, 2011 2:08 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
So talk to your Windows admins and ask what the resource limitations on that server are likely to be - memory will be the limiting factor I should think. I doubt that there is any documented limit as it will vary server-build-to-server-build, but you may wish to look at the SupportPac page, for the Performance Evaluation for W2K3 and WMQ V6.0. Even if you are not using that version of WMQ it will at least give you a rough idea. _________________ 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 |
|
 |
Volvic |
Posted: Tue May 31, 2011 4:37 am Post subject: |
|
|
Apprentice
Joined: 14 Oct 2009 Posts: 30
|
|
Back to top |
|
 |
SAFraser |
Posted: Tue May 31, 2011 1:42 pm Post subject: |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
svrconn chls may have up to 10 "conversations" on a single instance of the channel (from the same client machine). Only one TCP port is opened per instance. There are performance costs, however, so do consider your particular business requirements.
(Search for SHARECNV in the Info Center.) |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue May 31, 2011 8:12 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
SAFraser wrote: |
svrconn chls may have up to 10 "conversations" on a single instance of the channel (from the same client machine). Only one TCP port is opened per instance. There are performance costs, however, so do consider your particular business requirements.
(Search for SHARECNV in the Info Center.) |
And I would encourage you not to use this option before V7.0.1.5 as there is a number of fixes in the area.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
gbaddeley |
Posted: Wed Jun 01, 2011 4:35 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
SAFraser wrote: |
svrconn chls may have up to 10 "conversations" on a single instance of the channel (from the same client machine). Only one TCP port is opened per instance. There are performance costs, however, so do consider your particular business requirements.
(Search for SHARECNV in the Info Center.) |
Client apps must be multi threaded and configured to use this feature. A channel instance is not shared on a machine-wide basis, it can only be shared by threads in a single process. _________________ Glenn |
|
Back to top |
|
 |
SAFraser |
Posted: Thu Jun 02, 2011 3:47 am Post subject: |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
I don't think an app has to be multi-threaded. Our JMS application framework is 10 years old and it uses shared conversations without intervention. Maybe I am not understanding what gbaddeley is trying to tell me.  |
|
Back to top |
|
 |
shashivarungupta |
Posted: Thu Jun 02, 2011 7:37 am Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
Volvic wrote: |
Is one SVRCONN instance = TCP/IP connection? |
for mq v6
for ex, MQ JMS Multi-threaded app uses 'n' threads to connect to remote mq qmgr ., it would have 'n' tcp sockets , each one is independent ( and detected when connection is broken or used by client app for new connection )
for mq v7
for ex, MQ JMS Multi-threaded app uses 'n' threads to connect to remote mq qmgr., it would use 'only one' tcp socket for all communications , if that connection is broken it would be detected by both ends ( mq qmgr and client ) .
Its described here : (in outlines 4,5)
(correct me fjb_saper, if misunderstood some point here, its very delicate topic I believe)
 _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
|