Author |
Message
|
TonyD |
Posted: Sun Aug 26, 2007 9:13 pm Post subject: Broker won't deploy? |
|
|
Knight
Joined: 15 May 2001 Posts: 540 Location: New Zealand
|
I have just encountered a situation where a previously OK Windows broker suddenly stopped processing deployment messages. Messages just sat on SYSTEM.BROKER.EXECUTIONGROUP.QUEUE and queue status showed that no task had the queue open for output or input. I tried everything that I knew to try to sort out what I thought would be a minor problem but nothing worked! I deleted/recreated the broker, same for the CM, without any change in behavior. No error messages in the Event Viewer or the MQ logs, plenty of disk space, minimal CPU activity so no apparent reason why the software would not be working. Finally I have uninstalled and am reinstalling the broker software, which is real desperation.
Has anyone else encountered this behaviour? |
|
Back to top |
|
 |
AkankshA |
Posted: Mon Aug 27, 2007 7:56 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
mite be a configuration manager repository corruption case _________________ Cheers |
|
Back to top |
|
 |
mqmatt |
Posted: Tue Aug 28, 2007 2:57 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
The Configuration Manager's repository does not get corrupted. The universe surrounding it may become corrupted, but the repository is always good.
Seriously, the problem looks more like a bad DataFlowEngine (execution group). Check the flows deployed to the execution group for errors. And perhaps try creating a new execution group and deploying the flows there, to see if that fixes the problem.
If that doesn't work, ensure you're on the latest fixpack and raise a PMR. |
|
Back to top |
|
 |
whbrownnc |
Posted: Fri Aug 31, 2007 10:30 am Post subject: |
|
|
 Novice
Joined: 07 May 2003 Posts: 20 Location: Charlotte, NC
|
Just a thought. We have seen a situation where the file system hosting the Config Manager's working directory is full.
This may seem like an obvious thing... eventually it became obvious, but the syslog indicated a database error with the config mgr. (this is a WMB v6 config mgr running on AIX)
While the config mgr does not use a DB2 ConfgMgr DB anymore, my understanding is that it uses an internal DB to support its activity. _________________ Thanks,
Bill Brown
Integration Hosting and Services
IBM Certified - WMQ 6.0, 2008
IBM Certified - WMB 6.0, 2008 |
|
Back to top |
|
 |
Vitor |
Posted: Fri Aug 31, 2007 10:46 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
whbrownnc wrote: |
While the config mgr does not use a DB2 ConfgMgr DB anymore, my understanding is that it uses an internal DB to support its activity. |
Quite so. Though it can still use DB2. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
EddieA |
Posted: Fri Aug 31, 2007 12:19 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Vitor wrote: |
Quite so. Though it can still use DB2. |
No. Prior to V6, you had to use DB2. For V6, you have to use it's "internal DB". You have no choice.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
whbrownnc |
Posted: Fri Aug 31, 2007 12:22 pm Post subject: Broker won't deploy? |
|
|
 Novice
Joined: 07 May 2003 Posts: 20 Location: Charlotte, NC
|
cool.. I did not know that...
But concerning Tony D's original question... Tony... Did you check to see that the file system that supports your Config Manager's working directory (for us the file system is /var/mqsi) is not full? _________________ Thanks,
Bill Brown
Integration Hosting and Services
IBM Certified - WMQ 6.0, 2008
IBM Certified - WMB 6.0, 2008 |
|
Back to top |
|
 |
TonyD |
Posted: Sun Sep 02, 2007 3:16 pm Post subject: |
|
|
Knight
Joined: 15 May 2001 Posts: 540 Location: New Zealand
|
The problem happened on my Thinkpad. I did check that there was space on the disk ... about 6 Gb .., but certainly a valid suggestion ...thanks.
In the end, after wrestling with the problem for about 5 hours I am afraid I gave up and deciided to reinstall, without being really sure what this would achieve! As yet I have not recreated the CM and broker.
As I said, there were no error messages at all in the Event Log. In hindsight I should probably have tried MQMatt's suggestions ... but too late now. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Sep 02, 2007 3:42 pm Post subject: Re: Broker won't deploy? |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
TonyD wrote: |
I have just encountered a situation where a previously OK Windows broker suddenly stopped processing deployment messages. Messages just sat on SYSTEM.BROKER.EXECUTIONGROUP.QUEUE and queue status showed that no task had the queue open for output or input. I tried everything that I knew to try to sort out what I thought would be a minor problem but nothing worked! |
Did you try recycling the broker? If that did not help try deploying from the toolkit and check the status messages returned. Or try to deploy using mqsideploy and check what the error messages are.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
asudhakar |
Posted: Mon Sep 03, 2007 4:14 am Post subject: Re: Broker won't deploy? |
|
|
 Centurion
Joined: 12 May 2007 Posts: 116 Location: Bangalore
|
Hi
Previously i faced the same problem with :
DB2 7.3. MQ 5.3 WBIMB 5.0
Error. One or more errors occurred during the replacement of files (classesfiles) with files(classesfiles). Refer to the uninstall log of additional information.
2 times i uninstall MB and reinstalled.
so problem occurs due to sharing of class files.
Then finally i reinstall my OS nd again instal mb.
its working good in present.
If your problem not solved do the same task. _________________ WebSphere MQ, MB Support and Admin |
|
Back to top |
|
 |
|