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 Discussion » Upgrading to Tandem G06.25 and Up !!!! WARNING !!!!

Post new topic  Reply to topic
 Upgrading to Tandem G06.25 and Up !!!! WARNING !!!! « View previous topic :: View next topic » 
Author Message
hankknowles
PostPosted: Mon Nov 14, 2005 8:34 am    Post subject: Upgrading to Tandem G06.25 and Up !!!! WARNING !!!! Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

For HP Nonstop systems utilizing MQSeries V5.1 an issue that did have a severe impact under heavy message load.

We went to G06.25 and the Monday following this change a quirk began to appear. It manifested itself in the following way

1. Large quantities of messages were hanging in the queues but QPASA failed to identify a problem as the messages were indeed flowing but ever so slowly.

2.Process $MQ01 ( mqs-queue00) server's primary process was litterally in a long wait stat using minimal cpu or pages. While the backup process was claiming huge quantities of memory pages. The utilization on the backup process started running into the 80- 90% range.

3.The cpu that was running the backup process finally isssued a software halt took it's dump and reloaded.

4. Once we put humpty dumpty together again we discovered that the heap size comparison between primary and backup were vastly different the backup process' heap size was 8 times the size of the primary.

5. The software halt was caused my TMF process and it hung in a weird state and there was a transaction that would not end.

Upon investigation by HP and IBM support we found that the heap size was out of range between the two process', which is the culprit probably caused by the new native heap manager on the G06.25 O/S 1269 which you have to decide to use in the first place and we chose to go that route as we are running Java proc's to do encrypt and decrypt of all data in and out of this application. These process' really tax our system.

As it turns out if you are planning on going above G06.25 and you are using the new heap manager 1269, you need to make sure that you have CSD03 as well C3EFIX3 installed. Once these are in place you should be good to go!

Good Luck and be careful out there!
Back to top
View user's profile Send private message
AndyMQ
PostPosted: Tue Nov 15, 2005 4:33 am    Post subject: Reply with quote

Apprentice

Joined: 22 Apr 2004
Posts: 33
Location: Scotland

Hank, although it is only slightly related to MQ, we were very recently hit by a G06.25 problem which is there is a fix available for, but was never advertised as a "hot stuff". We've been running G06.25 since July with no real issues until last week when we lost 3 cpus on one cluster node one night, followed by 2 cpus on the same node and one on another node the next night.
It was a software halt (millicode) and the TFDS automatically rebooted them.
The problem was caused by a bug in G06.25 where PTLEs are not released when application processes complete before the PTLE expires.
It's one that just creeps up on you without warning. Our downfall was that we have pretty well balanced systems, so the PTLEs built up uniformly.
Just another one to watch out for. You can check your PTLEs either through Viewsys (F13) on by PEEK/CPU x/POOL. These numbers should be very low, probably single figures. If you have any showing in the hundreds or thousands, you need to apply the fix. Each processor will adjust to a maximum of 4777. If it hits that maximum, it's thank-you and goodnight!
Back to top
View user's profile Send private message
LuisFer
PostPosted: Tue Nov 15, 2005 8:38 am    Post subject: Reply with quote

Partisan

Joined: 17 Aug 2002
Posts: 302

We are running G06.26 from July and MQ on CSD3 with no Efix. We had a problem with the CMDSERV related with Heap Pages & degradation.
This one is resolved with Efix 4 (Dec-2005 at GA)
Back to top
View user's profile Send private message
hankknowles
PostPosted: Wed Nov 16, 2005 6:08 am    Post subject: Thanks for the heads up LUISFER Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

A question comes to mind as I will probably be going to .26 early next year! Did you change to new heap manager 1269 or stay with the old 8431 ( i think )???

Do you run any java on your systems I chasing extreme audit log rolling from the oss like 1 every 30 -60 minutes on our development system with Java4.2 installed?



LuisFer wrote:
We are running G06.26 from July and MQ on CSD3 with no Efix. We had a problem with the CMDSERV related with Heap Pages & degradation.
This one is resolved with Efix 4 (Dec-2005 at GA)
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 Discussion » Upgrading to Tandem G06.25 and Up !!!! WARNING !!!!
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.