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 » WebSphere Message Broker (ACE) Support » Config Manager hangs up after update to MB6.1.0.2

Post new topic  Reply to topic
 Config Manager hangs up after update to MB6.1.0.2 « View previous topic :: View next topic » 
Author Message
sebastianhirt
PostPosted: Thu Jun 12, 2008 4:40 am    Post subject: Config Manager hangs up after update to MB6.1.0.2 Reply with quote

Yatiri

Joined: 07 Jun 2004
Posts: 620
Location: Germany

All,

I have updated one of my Configmanagers to 6.1.0.2 on an AIX(5.3) box yesterday. For the first 24 hours or so it did work as a charm. But now, every couple of hours the damn thing freezes (i.e. Processes are still there but can't connect to it using the Toolkit). Restarting fixes the Prob at first, but it commes back after some time.

What it makes difficult, is that there are:
- no Abend files,
- no entries to the syslog,
- no entries to MQ logs

Any ideas, open PMRs ifixes around? Or is it PMR time for me?
Back to top
View user's profile Send private message
mqmatt
PostPosted: Thu Jun 12, 2008 8:42 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

Are you asking the Config Manager to do anything at the time it stops responding?

If not, the fact that it only happens every so often suggests it might be a issue with CM/broker synchronisation (though this occurs every hour, by default)... you could try disabling synchronisation temporarily by setting the environment variable MQSIJVERBOSE=-DMQSI_SYNCTIMEMINSOVERRIDE=-1
I wouldn't recommend running like this permanently.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Jun 12, 2008 12:39 pm    Post subject: Reply with quote

Grand High Poobah

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

Sebastian:
Have your network guys check carefully your network and active directory.
I have had the case on windows where the DNS server kept throwing the conf mgr's box out of the list. You might have a communications problem...

Ykes
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
sebastianhirt
PostPosted: Thu Jun 12, 2008 11:35 pm    Post subject: Reply with quote

Yatiri

Joined: 07 Jun 2004
Posts: 620
Location: Germany

Matt,

Is this the thing that is causing the 'Report' error Messages on a V6.0 Broker? I am having those around. Opened a PMR some time back but haven't heard anything from IBM since over a month. One would think that it doesn't take you a month to read trough some trace files, but that's another story.
This also was my original motiviation to update. 6.1.0.1 did run pretty well for us. And in deed that problem was fixed, but now my Config Manager is not quiet running as I want it to.

I had restarted it yesterday evening, and it was still responding in the morning. So I wouldn't want to believe that it is the syncronisation thing. Do you think the variable you suggested is worth trying anyway?

There are some users on the box deploying things. That's usually when it starts to hang.

Fjb,
Don't believe so. Can Telnet the Server. It's only the configmanager that doesn't responde to my connection wishes.
Anyway. I will get somebody to check this when it happens for the next time.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Fri Jun 13, 2008 2:03 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

CM/Broker synchronisation will cause the report messages to appear on the broker's admin queue (synchronisation uses the same technique of retrieving the data as mqsilist/mqsireportproperties), though there is a relatively short expiry time set on these messages so they shouldn't build up over time.

Service trace should tell you (or IBM ) what's going on, but as the problem takes a while to reproduce, start the trace after the CM has been running for a while, and also set a large log size. For how to change the log size, see the bottom of my article here: http://www.ibm.com/developerworks/websphere/library/techarticles/0706_lucas/0706_lucas.html
(It involves changing the registry. Hands up, I have an open product feature from Dec 1999 to make changing the log size easier for the CM )
Back to top
View user's profile Send private message
jsware
PostPosted: Fri Jun 13, 2008 2:25 am    Post subject: Reply with quote

Chevalier

Joined: 17 May 2001
Posts: 455

If you are on AIX5.3 ML7, IBM recommend you apply a fix to the C/C++ runtime environment as unpredicable failures can occur.

See http://www-1.ibm.com/support/docview.wss?rs=849&context=SSKM8N&context=SS3GH2&context=SSKMAB&q1=IZ09358&uid=swg21300071&loc=en_US&cs=utf-8&lang=en

It seems to have cured my DataFlowEngine problems when pushing through 100s of messages/second.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price.
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 » WebSphere Message Broker (ACE) Support » Config Manager hangs up after update to MB6.1.0.2
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.