| Author |
Message
|
| msiegert |
 Posted: Mon Nov 26, 2001 5:44 am Post subject: |
 |
|
Apprentice
Joined: 05 Aug 2001
Posts: 29
|
Hi!
I'm working with MQSeries 5.2 on SunOs 5.6:
The value of shared memory in etc/system is set to the following:
*MQSeries Parameter*
set shmsys:shminfo_shmmax = 4194304
I've now found another value concerning the kernel configuration in MQSeries for Sun Solaris Quick Beginnings Version 5 .2 which is:
set shmsys:shminfo_shmmax =4294967295
What is your experience?
Which value did you set?
Is it possible that the following error occurs because of my kernel configuration?
Thanks for help.
regards Marc
-------------------------------------------------------------------------------
11/25/01 02:27:17
AMQ6119: An internal MQSeries error has occurred ('Too many open files' from
shmat.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The
MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
11/25/01 02:27:17
AMQ6184: An internal MQSeries error has occurred on queue manager BA22.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 7956.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
|
|
| Back to top |
|
 |
| Pierre-Yves Lesage |
| Posted: Tue Nov 27, 2001 4:02 am Post subject: |
|
|
Novice
Joined: 21 Aug 2001
Posts: 17
Location: London, UK
|
Hi,
I am not sure if your error comes from your /etc/system set-up but we are using shmsys:shminfo_shmmax = 4194304 as suggested in the documentation. It appears to be adequate on our servers to cope with heavy load and usage at an enterprise level. We are using MQSeries 5.1 and Solaris 2.6 (sunOs 5.6).
You might want to tune-it up only if you have another application (like Oracle) that uses semaphores and shared memory.
Cheers,
Pierre-Yves
[ This Message was edited by: Pierre-Yves Lesage on 2001-11-27 04:03 ] |
|
| Back to top |
|
|
| bduncan |
| Posted: Thu Dec 06, 2001 10:34 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
I've found that without setting kernel parameters to AT LEAST what is recommended in the quick beginnings guide, you won't get anywhere, even under light load. And I agree, the values in quick beginnings should be sufficient for even enterprise installs assuming that you don't have any other intensive applications like Oracle running on the same machine...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| Shalini |
| Posted: Thu Oct 14, 2004 3:15 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi All,
We are facing the problem for each 3 days with our QM failing to another node in a Cluster due to the FDC
(Probe Description :- AMQ6035: MQSeries failed, no storage available.),
Major Errorcode :- xecS_E_NO_MEM |
Minor Errorcode :- OK |
Probe Id :- XY132001
Major Errorcode :- xecS_E_NO_MEM
We have given the Same kernal Params specified in Solaris Quick begnings
Is there any way to avoid the error (FDC) I donot know how much more I can increase the kernal values ???
Is that double or triple of that value specified in Solaris quick begnins ???
Please help
 |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Oct 14, 2004 6:13 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| Shalini |
| Posted: Wed Oct 20, 2004 5:13 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi,
MQ 5.2 CSD7
We have the a issues of kernal params of MQ.
| Quote: |
We are facing the problem for each 3 days with our QM failing to another node in a Cluster due to the FDC
(Probe Description :- AMQ6035: MQSeries failed, no storage available.),
Major Errorcode :- xecS_E_NO_MEM |
Minor Errorcode :- OK |
Probe Id :- XY132001
Major Errorcode :- xecS_E_NO_MEM
|
We have a exit programe, I belive the exit is one who is the culprit and I have decided to test the samephore values with and without exit in the QMGR.
what is name of the process under which exit runs ???.
The only info I got about the process are
ProcName Process Function
amqhasmx logger
amqharmx log formatter, used only if the queue manager has linear logging selected
amqzllp0 checkpoint processor
amqzlaa0 queue manager agents
amqzxma0 processing controller
But I donot what is the name of the exit process name, to check its samephore.
Please help
|
|
| Back to top |
|
|
| siliconfish |
| Posted: Fri Oct 22, 2004 3:46 pm Post subject: |
|
|
Master
Joined: 12 Aug 2002
Posts: 203
Location: USA
|
All the API Exits run in FASTPATH Binding and the CLWL Exit mode can be specified in the option CLWLMode and Channel exits which run outside the queue manager as part of MCA.
So I don't think its possible to get the process id of the exit as it is running in FASTPATH binding.
_________________
siliconfish |
|
| Back to top |
|
|
| Shalini |
| Posted: Mon Oct 25, 2004 3:39 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
| Quote: |
| CLWLMode and Channel exits which run outside the queue manager as part of MCA |
Hi siliconfish,
1) Is there any way to find the process for Channel Exit
2) for Cluster work load exit
if not for API Exit 
Please suggest
 |
|
| Back to top |
|
|
|
|
