| Author |
Message
|
| natis |
 Posted: Wed May 29, 2002 5:43 am Post subject: AMQ6035 MQSeries failed, no storage available(MQ5.2/SUN) |
 |
|
Newbie
Joined: 29 May 2002
Posts: 1
Location: Israel
|
Hi ,
Has anyone faced this error in the error log .
AMQ6035 MQSeries failed, no storage available.
Explanation: An internal function of the product attempted to obtain storage, but there was none available.
User Response: Stop the product and restart it. If this does not resolve the problem, save the generated output files and contact your IBM support center.
can someone give me some suggestions what should I do in this situation
I get message when running strmqm, (MQ5.2 on SUN )
Logging is circular.
Thanks in Advance.
Mark
P.S
Here is the log :
| LVLS :- 520 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- XY132001 |
| Application Name :- MQM |
| Component :- xstCreateExtent |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- 00001015 (mqtest) |
| Program Name :- amqzxma0_nd |
| Process :- 00010606 |
| Thread :- 00000001 |
| QueueManager :- AF_P_01 |
| Major Errorcode :- xecS_E_NO_MEM |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6035 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6035: MQSeries failed, no storage available. |
| Comment1 :- Could not allocate a new shared memory extent |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Wed May 29, 2002 6:10 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Sounds like you need to tune the kernels shared memory size see
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/amqdac03/amqdac03tfrm.htm
To change the values, add a set parameter = value line to the /etc/system file. For further information on setting up the system, see the Sun Solaris System Administration documentation.
Figure 1. Kernel parameter values - example setting on a Solaris system
set shmsys:shminfo_shmmax = 4294967295
set shmsys:shminfo_shmseg = 1024
set shmsys:shminfo_shmmni = 1024
set semsys:seminfo_semaem = 16384
set shmsys:shminfo_semmni = 1024
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmns = 16384
set semsys:seminfo_semmsl = 100
set semsys:seminfo_semopm = 100
set semsys:seminfo_semmnu = 2048
set semsys:seminfo_semume = 256
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 4096
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Wed May 29, 2002 6:31 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi,
by the way, have you KILL'ed some MQSeries processes ?
I've got the same problem some time ago, (caused by KILLing processes), we had to restart the machine, I didn't nkow if there was a command to free up shared storage.
My tiny bit. 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| Leafar |
| Posted: Wed May 14, 2003 12:27 pm Post subject: AMQ6035 MQSeries failed, no storage available. |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
Try this...
stop the qmanager
endmqm -i qmgr
remove all memory segments that belongs to mqm
ipcs -m | grep mqm
ipcrm -m MID
do the same for all the semaphores an message queue
Saludos
Rafael |
|
| Back to top |
|
|
| Shalini |
| Posted: Thu Oct 14, 2004 1:23 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi All,
We have faced the same problem and same FDC generated in our production box of same confiration MQ5.2 CSD7 with Solaris 2.8.
We have set the following values for kernal params
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set semsys:seminfo_semmsl=200
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set shmsys:shminfo_shmseg = 1024
set shmsys:shminfo_shmmni = 2048
set semsys:seminfo_semaem = 16384
set semsys:seminfo_semmni = 2048
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmns = 32768
set semsys:seminfo_semmnu = 4096
set semsys:seminfo_semume = 256
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 4096
set rlim_fd_cur = 1024
I have few Queries
1) Can I increase the values as we have our production QM(Production) get restarted once in a 3 days due to this FDC (Production QM are in O.S Cluster).
2) What the PDF suggest is
| Quote: |
Kernel configuration
WebSphere MQ uses semaphores, shared memory, and file descriptors, and it is
probable that the default kernel configuration is not adequate. |
1) If I want to increase can I do a double or triple or quadraple these value.
2) Can any one suggest what is the maximum value for each kernal value
I can give for all the kernal params.
3) Even If I give some value lower than the max value and my QM reports the same FDC, how to resolve the issue Witout restarting the production QM
Is there any Long term fix for the same.
Note: We don't have the rights to stop or start QM it automatically failover in cluster environment this Cluster env is managed by external party.
So each time we request for restart we have to face our client badly.
Please help
 |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Oct 14, 2004 2:35 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| On Solaris changed kernel parameters only take effect when the machine is rebooted. |
|
| Back to top |
|
|
| Shalini |
| Posted: Thu Oct 14, 2004 3:08 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi,
But my question is what could be the problem its asking for more shared memory. Is there any fix for the same so that I donot get such FDC.
|
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Oct 14, 2004 6:15 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
|
|
