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 » contact admin Solaris Kernel Setting

Post new topic  Reply to topic
 contact admin Solaris Kernel Setting « View previous topic :: View next topic » 
Author Message
chuckf99
PostPosted: Mon Sep 08, 2008 7:34 am    Post subject: contact admin Solaris Kernel Setting Reply with quote

Novice

Joined: 05 Jan 2007
Posts: 22

I'm not sure if anyone can help, but one of our consultants just asked me to see if we could get this figured out:

He is concerned that he may not have enough semaphores configured as a Qmgr is suffering from semaphore wait timeouts.


Simple description of the environment.

Pair of Sun x4200 x2 dual core AMD 8GB ram VCS cluster
Currently 15 Qmgrs running across the VCS cluster
Qmgrs hosted on these servers with applications using MQClient to connect. Can have up to 8000 client connections to the cluster.

Current Kernel Parameters
set shmsys:shminfo_shmmax=4294967295
set semsys:shminfo_shmmni=1024
set semsys:seminfo_semmni=1024
set semsys:seminfo_semmsl=100
set semsys:seminfo_semopm=100
set msgsys:msginfo_msgmni=50
set msgsys:msginfo_msgmnb=65535
* Semaphore changes for BMC
set semsys:seminfo_semmns=748
set semsys:seminfo_semmni=1368
set semsys:seminfo_semmnu=354
set shmsys:shminfo_shmseg=350
set shmsys:shminfo_shmmni=1368
* End BMC semaphore changes

Sample qm.ini settings
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#* *#
#* *#
Log:
LogPrimaryFiles=48
LogSecondaryFiles=2
LogFilePages=16384
LogType=CIRCULAR
LogBufferPages=512
LogPath=/MQHA/MEMQSSC1/log/MEMQSSC1/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=13
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib64/amqzfu
ComponentDataSize=0
Channels:
MaxChannels=500
MaxActiveChannels=500
Tcp:
KeepAlive=Yes


I do need to be able to have one server support all the Qmgrs running on it.

Thanks,

Chuck Fried
TxMQ, Inc.
_________________
Chuck Fried
TxMQ, Inc
716-564-1700 ext 22
chuck@txmq.com
Back to top
View user's profile Send private message Send e-mail MSN Messenger
jeevan
PostPosted: Mon Sep 08, 2008 9:09 am    Post subject: Re: contact admin Solaris Kernel Setting Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

chuckf99 wrote:
I'm not sure if anyone can help, but one of our consultants just asked me to see if we could get this figured out:

He is concerned that he may not have enough semaphores configured as a Qmgr is suffering from semaphore wait timeouts.


Simple description of the environment.

Pair of Sun x4200 x2 dual core AMD 8GB ram VCS cluster
Currently 15 Qmgrs running across the VCS cluster
Qmgrs hosted on these servers with applications using MQClient to connect. Can have up to 8000 client connections to the cluster.

Current Kernel Parameters
set shmsys:shminfo_shmmax=4294967295
set semsys:shminfo_shmmni=1024
set semsys:seminfo_semmni=1024
set semsys:seminfo_semmsl=100
set semsys:seminfo_semopm=100
set msgsys:msginfo_msgmni=50
set msgsys:msginfo_msgmnb=65535
* Semaphore changes for BMC
set semsys:seminfo_semmns=748
set semsys:seminfo_semmni=1368
set semsys:seminfo_semmnu=354
set shmsys:shminfo_shmseg=350
set shmsys:shminfo_shmmni=1368
* End BMC semaphore changes

Sample qm.ini settings
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#* *#
#* *#
Log:
LogPrimaryFiles=48
LogSecondaryFiles=2
LogFilePages=16384
LogType=CIRCULAR
LogBufferPages=512
LogPath=/MQHA/MEMQSSC1/log/MEMQSSC1/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=13
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib64/amqzfu
ComponentDataSize=0
Channels:
MaxChannels=500
MaxActiveChannels=500
Tcp:
KeepAlive=Yes


I do need to be able to have one server support all the Qmgrs running on it.

Thanks,

Chuck Fried
TxMQ, Inc.


Is there any entry in log file such as AMQ6150? Is there any FDC generated with probe id: XC307070?


Also, it would be useful if you can give little scenario eg. action and response? can this be reproduced? when it happens?
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Sep 08, 2008 9:47 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

15 QMs on 1 pair of servers? Ugh. Not the best design.

You won't find any recomendations officially on how to tune a system for that, but check out these 2 links:

How to configure UNIX IPC resources for WebSphere MQ

Resource limit configuration
_________________
Peter Potkay
Keep Calm and MQ On


Last edited by PeterPotkay on Mon Sep 08, 2008 9:51 am; edited 1 time in total
Back to top
View user's profile Send private message
jeevan
PostPosted: Mon Sep 08, 2008 9:48 am    Post subject: Re: contact admin Solaris Kernel Setting Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

chuckf99 wrote:
I'm not sure if anyone can help, but one of our consultants just asked me to see if we could get this figured out:

He is concerned that he may not have enough semaphores configured as a Qmgr is suffering from semaphore wait timeouts.


Simple description of the environment.

Pair of Sun x4200 x2 dual core AMD 8GB ram VCS cluster
Currently 15 Qmgrs running across the VCS cluster
Qmgrs hosted on these servers with applications using MQClient to connect. Can have up to 8000 client connections to the cluster.

Current Kernel Parameters
set shmsys:shminfo_shmmax=4294967295
set semsys:shminfo_shmmni=1024
set semsys:seminfo_semmni=1024
set semsys:seminfo_semmsl=100
set semsys:seminfo_semopm=100
set msgsys:msginfo_msgmni=50
set msgsys:msginfo_msgmnb=65535
* Semaphore changes for BMC
set semsys:seminfo_semmns=748
set semsys:seminfo_semmni=1368
set semsys:seminfo_semmnu=354
set shmsys:shminfo_shmseg=350
set shmsys:shminfo_shmmni=1368
* End BMC semaphore changes

Sample qm.ini settings
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#* *#
#* *#
Log:
LogPrimaryFiles=48
LogSecondaryFiles=2
LogFilePages=16384
LogType=CIRCULAR
LogBufferPages=512
LogPath=/MQHA/MEMQSSC1/log/MEMQSSC1/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=13
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib64/amqzfu
ComponentDataSize=0
Channels:
MaxChannels=500
MaxActiveChannels=500
Tcp:
KeepAlive=Yes


I do need to be able to have one server support all the Qmgrs running on it.

Thanks,

Chuck Fried
TxMQ, Inc.


Chuck,

Although not directly related to you problem, I would do certain configuration differently. However it is up to you>

1. I would have log primary to log secondary as 3:2 rations instead havding a large primary and small secondar. IBM suggests this indirectly giving 3 primary and 2 secondary files as default.

2. I would not have values of both MaxChannels, and MaxActiveChannels the same. I would keep certain channel for coming up the inactive channel i.e. I would have MaxActiveChannels=480 ( 490 but not 500).

3. I would probably increase the LogBufferPages to max 4096 depending the message size.

http://www.ibm.com/developerworks/websphere/library/techarticles/0712_dunn/0712_dunn.html
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Sep 08, 2008 9:50 am    Post subject: Re: contact admin Solaris Kernel Setting Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

jeevan wrote:

2. I would not have values of both MaxChannels, and MaxActiveChannels the same. I would keep certain channel for coming up the inactive channel i.e. I would have MaxActiveChannels=480 ( 490 but not 500).

I don't understand jeevan. Please elaborate.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
chuckf99
PostPosted: Mon Sep 08, 2008 9:51 am    Post subject: FDC probe id Reply with quote

Novice

Joined: 05 Jan 2007
Posts: 22

Yes and yes, we are getting AMQ61507 and the FDC probe id is XC307070.



If we use runmqsc QmgrName, it just hangs. And it is repeatable.
_________________
Chuck Fried
TxMQ, Inc
716-564-1700 ext 22
chuck@txmq.com
Back to top
View user's profile Send private message Send e-mail MSN Messenger
jeevan
PostPosted: Mon Sep 08, 2008 10:18 am    Post subject: Re: contact admin Solaris Kernel Setting Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

PeterPotkay wrote:
jeevan wrote:

2. I would not have values of both MaxChannels, and MaxActiveChannels the same. I would keep certain channel for coming up the inactive channel i.e. I would have MaxActiveChannels=480 ( 490 but not 500).

I don't understand jeevan. Please elaborate.


I mean I would not have

MaxChannels=500
MaxActiveChannels=500

rather I would have the value of MaxActiveChannels less than that of
MaxChannels.

My understanding is, lets say if there are 10 inactive connections, and we set both max and maxactive channel same, all the connection will be allowd and when the application which was connected and the connection was inactive would like to put/get message, has to abandone the connection and has to try again. In order to avoid this, we will leave certain connection aside.

I may be wrong but I practice this. I also assume that if there is no other values of the maxactive, why IBM has this attribute? I hope you could shed light on it.

thanks
Back to top
View user's profile Send private message
jeevan
PostPosted: Mon Sep 08, 2008 10:23 am    Post subject: Re: FDC probe id Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

chuckf99 wrote:
Yes and yes, we are getting AMQ61507 and the FDC probe id is XC307070.



If we use runmqsc QmgrName, it just hangs. And it is repeatable.


Chuck,

Do you su to mqm and run this comman ? I had a strange problem in solaris 10 a while ago.

When the number of queue managers were less, it was running okay, but after qmgrs reaches certain number it start giving some problem. Eventually, when we started running as mqm ( su mqm), it worked okay.

I am just wondering.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Sep 08, 2008 11:28 am    Post subject: Re: contact admin Solaris Kernel Setting Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

jeevan wrote:
PeterPotkay wrote:
jeevan wrote:

2. I would not have values of both MaxChannels, and MaxActiveChannels the same. I would keep certain channel for coming up the inactive channel i.e. I would have MaxActiveChannels=480 ( 490 but not 500).

I don't understand jeevan. Please elaborate.


I mean I would not have

MaxChannels=500
MaxActiveChannels=500

rather I would have the value of MaxActiveChannels less than that of
MaxChannels.

My understanding is, lets say if there are 10 inactive connections, and we set both max and maxactive channel same, all the connection will be allowd and when the application which was connected and the connection was inactive would like to put/get message, has to abandone the connection and has to try again. In order to avoid this, we will leave certain connection aside.

I may be wrong but I practice this. I also assume that if there is no other values of the maxactive, why IBM has this attribute? I hope you could shed light on it.

thanks


MaxChannels=500
MaxActiveChannels=490

If you have 490 active channels, you cannot start anymore, regardless if MaxChannels is 10 more or 100 more or the same as MaxActiveCHannels.


http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.amqzag.doc/fa12670_.htm
Quote:

Channels

Use the Channels queue manager properties page from the WebSphere® MQ Explorer, or the CHANNELS stanza in the qm.ini file, to specify information about channels.

MaxChannels=100|number
The maximum number of channels allowed. The default is 100.
MaxActiveChannels=MaxChannels_value
The maximum number of channels allowed to be active at any time. The default is the value specified on the MaxChannels attribute.

_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
jeevan
PostPosted: Mon Sep 08, 2008 12:04 pm    Post subject: Re: contact admin Solaris Kernel Setting Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

PeterPotkay wrote:
jeevan wrote:
PeterPotkay wrote:
jeevan wrote:

2. I would not have values of both MaxChannels, and MaxActiveChannels the same. I would keep certain channel for coming up the inactive channel i.e. I would have MaxActiveChannels=480 ( 490 but not 500).

I don't understand jeevan. Please elaborate.


I mean I would not have

MaxChannels=500
MaxActiveChannels=500

rather I would have the value of MaxActiveChannels less than that of
MaxChannels.

My understanding is, lets say if there are 10 inactive connections, and we set both max and maxactive channel same, all the connection will be allowd and when the application which was connected and the connection was inactive would like to put/get message, has to abandone the connection and has to try again. In order to avoid this, we will leave certain connection aside.

I may be wrong but I practice this. I also assume that if there is no other values of the maxactive, why IBM has this attribute? I hope you could shed light on it.

thanks


MaxChannels=500
MaxActiveChannels=490

If you have 490 active channels, you cannot start anymore, regardless if MaxChannels is 10 more or 100 more or the same as MaxActiveCHannels.

If so, what is the use of the maxchannel attribute as the default values is maxchannel already.

MaxActiveChannels=MaxChannels_value
The maximum number of channels allowed to be active at any time. The default is the value specified on the MaxChannels attribute.




http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.amqzag.doc/fa12670_.htm
Quote:

Channels

Use the Channels queue manager properties page from the WebSphere® MQ Explorer, or the CHANNELS stanza in the qm.ini file, to specify information about channels.

MaxChannels=100|number
The maximum number of channels allowed. The default is 100.
MaxActiveChannels=MaxChannels_value
The maximum number of channels allowed to be active at any time. The default is the value specified on the MaxChannels attribute.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Sep 08, 2008 2:28 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

To put it a little bit more clearly... and from what I remember vaguely...
Max Channels refers to the max # of channels that you can define before the qmgr gives you an evil errorcode....
Max Active Channels is the max # of channels (including channel instances) the qmgr allows you to start before it gives you a resource busy....

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » contact admin Solaris Kernel Setting
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.