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 » AMQ6037 on Windows platform

Post new topic  Reply to topic
 AMQ6037 on Windows platform « View previous topic :: View next topic » 
Author Message
DarthMouse
PostPosted: Fri Aug 06, 2004 3:19 am    Post subject: AMQ6037 on Windows platform Reply with quote

Newbie

Joined: 04 Aug 2004
Posts: 7
Location: Denmark

Hi

I got a lot of AMQ6037 errors on a windows 2000 server. The MQSeries version is 5.2.1.

Sadly there are no FDC files or any other related MQSeries or operating system errors.

There was no shortege of memory, disk space or overload on the CPU.

The Queue manager reporting the error continued to work, but a few queues 'hung' all other queues kept working fine. The problem could not be related to one or more channels. The messages where persistent and when the queue manager was rebooted everything worked fine again.

No service pack was installed and no other chances had been made to the system in recent time.

The queue manager did have a good load at the time, but I was unable to check the filesystem load at the time of the problem.

As the version is unsupported there is no official help to be gained.

I read somewhere else that semaphores could be related to this, but on a unix system. I going with that at the moment, but the road is pretty dark.

If anybody has any knowledge of what the AMQ6037 relates too and possible identification of the problem causing this, i would be most grateful.
Back to top
View user's profile Send private message
kman
PostPosted: Mon Aug 09, 2004 7:51 pm    Post subject: Reply with quote

Partisan

Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia

Code:
 536895543  0x20006037  xecS_E_NONE

MESSAGE:
WebSphere MQ was unable to obtain enough storage.

EXPLANATION:
The product is unable to obtain enough storage.  The product's error recording
routine may have been called.

ACTION:
Stop the product and restart it.  If this does not resolve the problem see if a
problem has been recorded.  If a problem has been recorded, 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.



Restarting was as suggested. I would recommend you look at the latest fixes/CSDs for your MQ version. Follow the News and Updates forum for such. It should still be available. The best thing is to apply the latest fixes.

On the other hand, as this message says storage, I would think that refers to the hard disk. Wow!! never seen that before. The messages were persistent, so that explains a bit on the storage requirement. Have you look at the log file size? What other errors reported in the error log? How big is the max message size?
Back to top
View user's profile Send private message Yahoo Messenger
DarthMouse
PostPosted: Mon Aug 09, 2004 11:55 pm    Post subject: Reply with quote

Newbie

Joined: 04 Aug 2004
Posts: 7
Location: Denmark

Hi Kman

Thanks for the answer.

There are 20 primary log files at 4095 x 4Kb and 2 secondary log files.

The log file usage wasn't checked at the time of the restart. But I doubt it has anything to do with these as messages kept coming on all the other queues. The error only effected some 20 queues out of about 200.

There where no other errors in either of the MQ error logs or the eventlog. Except for a couple of queue high/low events (%5 full warning). The warning was on queues working fine.

The max message size are queue/channel specific from 1Mb to 10Mb but the queues that failed had a standard 4194304. The channel they used was also being used for other queues, that worked fine.

I'm not sure if the latest fix was installed at the time of the error. I'll have to check that.

I agree that storage would indicate hard disks, but with 60 Gb free I'm as amassed as you are.

Anyway the error hasn't shown up since, so that at least is something, but I'm just a bit unhappy not understanding what went wrong, and being unable to understand the no storage available event.

Thanks again for the answer, and best wishes from here.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » AMQ6037 on Windows platform
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.