| Author |
Message
|
| hcibm |
 Posted: Mon Aug 16, 2004 10:13 am Post subject: Windows not affected by change to MAXCHANNELS setting |
 |
|
Novice
Joined: 03 Aug 2004
Posts: 18
|
hi,
we are hitting the maxchannels reached problem on windows (xp). when we bump up the MAXACHANNELS and MAXACTIVECHANNEL settings and restart the queue manager, we don't see the change being reflected and we still get the same maxchannels reached error.
we are using mq5.3 with csd5.
any help in this is greatly appreciated. thanks.
regards,
-hcibm |
|
| Back to top |
|
 |
| hcibm |
| Posted: Mon Aug 16, 2004 10:49 am Post subject: |
|
|
Novice
Joined: 03 Aug 2004
Posts: 18
|
do we need to modify any registry settings? or do we need to move to windows 2000/nt? we are currently on windows xp.
-hcibm |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Aug 16, 2004 11:09 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
XP home? Or Pro? XP home is not supported. But on XP Pro if you changed that value, and restarted the QM to boot, then the change should have taken. What number are you trying to stick in there?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| hcibm |
| Posted: Mon Aug 16, 2004 11:13 am Post subject: |
|
|
Novice
Joined: 03 Aug 2004
Posts: 18
|
Thanks Peter for your prompt reply.
We are using xp pro, we changed the maxchannels number to 2000.
Regards,
-hcibm |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Aug 16, 2004 11:17 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Are you sure you just didn't hit 2000 channels right away?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| hcibm |
| Posted: Mon Aug 16, 2004 11:22 am Post subject: |
|
|
Novice
Joined: 03 Aug 2004
Posts: 18
|
Nope. We have far less than 200 channels being used may be. we just picked a huge number to play with. also the MAXACTIVECHANNELS is set to 256.
do you think we need to touch/change any registry settings?
regrards,
-hcibm |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Aug 16, 2004 11:47 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
No need to mess with the registry.
You have MaxChannel set to 2000, but MaxActive set to 256? Kinda backwords, but OK.
Set both to the same #, or leave MaxActiveBlank and it will default to what you have in MaxChannels, bounce the QM and try again.
Then do a display Channel Status with a * to see exactly how many channels the QM thinks are active, instead of how many you think are active.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| hcibm |
| Posted: Mon Aug 16, 2004 1:03 pm Post subject: |
|
|
Novice
Joined: 03 Aug 2004
Posts: 18
|
We changed both maxchannels and maxactivechannels to be 2048 and also restarted the queue manager. Still no luck!
Regards,
-hcibm |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Aug 16, 2004 4:24 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If there is nothing else in the error logs, and you are doing everything as you say you, then its probably time to open up a PMR with IBM.
I still wonder though at how many channels running you are getting that error. What I mean is, you may have a runaway app that is creating connections as fast as possible, and no matter what you set the # to, you will hit it. Or is this a problem where you are getting the error even though you really and trully only have a couple hundred channels running.
Display Channel Status (*) would tell us this.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
