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 » Broker problem

Post new topic  Reply to topic
 Broker problem « View previous topic :: View next topic » 
Author Message
Nizam
PostPosted: Mon Jul 26, 2004 6:15 pm    Post subject: Broker problem Reply with quote

Disciple

Joined: 10 Feb 2004
Posts: 160
Hi Guys,
We had this dicussion last week on this boad.
http://www.mqseries.net/phpBB2/viewtopic.php?t=16500
But now I have these problems....
1. Topology configuration does not get updated in the tool kit.
2. Messages gets piled up on SYSTEM.BROKER.EXECGROUP.QUEUE and other queues.
3. I deleted a particular rogue flow that rethrows exceptions multiple times(800 errors) because of an error in esql. Even after deleting this from the execution group, I see unexpected results...I actually see the same results that I got before deleting the flows.

I have problems with this broker very frequently and I had to stop the broker somehow and restart the server in the worst case.

I am running 3 brokers on windows 2000 server..

Any ideas guys......
Thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Jul 27, 2004 4:54 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
I don't see what fixpack you're running - I hope you're running FP3.

Are you seeing errors in your event logs?

If a message flow gets caught in a loop, the execution group that is running that flow will not respond to anything - this could explain the messages piling up in the EXECGROUP queue. And messages piling up in the EXECGROUP queue means that the execution group isn't actually doing the deployment changes you ask - so it's not going to respond to the tooling for the tooling to update.

You might consider deleting and recreating your execution groups. Or at a minimum, doing a complete redeploy.

One way to halt an execution group that has gone unresponsive is this: Get-Disable all queues that message flows in that group are reading from. Use mqsilist <brokername> to identify the process ID of the execution group. Kill the execution group process. The execution group should then start up in a state where it's not doing anything (other than trying to read from get-disabled queues) and should respond to deployment commands.
_________________
I am *not* the model of the modern major general.
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 » Broker problem
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.