| Author |
Message
|
| reshds |
 Posted: Mon Nov 29, 2010 3:58 pm Post subject: ! execution group is not running ! |
 |
|
Apprentice
Joined: 25 Mar 2010
Posts: 37
Location: LA
|
I am using WebSphere Message Brokers Toolkit - Message Broker Version: 6.0.2
I have deleted the borker and recreated Now I tried configuring the broker from toolkit. But I am getting two alerts saying that
Broker is not running...
execution group is not running
Please let me know what is wrong .Thank you, |
|
| Back to top |
|
 |
| harish_td |
| Posted: Mon Nov 29, 2010 6:31 pm Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
Are the channels between the Config Manager and the Broker Queue Manager are running?
What happens when you disconnect the config manager and connect back to it from the toolkit?
What happens when you deploy a flow to this execution group? |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Mon Nov 29, 2010 9:43 pm Post subject: Re: ! execution group is not running ! |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| reshds wrote: |
...
Broker is not running...
execution group is not running
... |
Did you try to install one Flow? Execution Group will only start to run after first successful deployment.
Are the windows services (broker, config manager) up and running?
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| reshds |
| Posted: Tue Nov 30, 2010 11:32 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2010
Posts: 37
Location: LA
|
j.f and Harish ,
Thanks for the reply. I tried installing one flow. but still the issue was there.
There was some issue with broker so I thought of doing it again.
I have deleted the configManager and BrokerDatabase .but now not able to delete the Broker .I am getting the folowing error
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he ODBC return code was '-1'. See the following messages for information obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text
''[Microsoft][ODBC Driver Manager] Data source name not found and no default dr
iver specified''.
The error has the following diagnostic information: SQL State ''
IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][OD
BC Driver Manager] Data source name not found and no default driver specified''
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified
when the broker was created.
Check that the database is running, that an ODBC connection has been created and
that the userid and password pair specified for ODBC connect on the mqsicreate
command are capable of being used to connect to the database using an ODBC conne
ction. Also ensure that the database has a adequate number of database connectio
ns available for use.
Please let me know how to delete the broker now.Thanks in Advance. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 30, 2010 11:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| reshds wrote: |
| There was some issue with broker so I thought of doing it again. |
What issue?
| reshds wrote: |
| Please let me know how to delete the broker now. |
Well you could try deleting the broker before deleting the database it uses, like it says in the documentation, next time and saving yourself a lot of trouble.
As you've decided not to do that, now you need to either restore the database from a back up or use the procedure in the documentation described as a "last resort" to remove the broker.
You might also want to give some thought to not diagnosing & resolving problems by randomly issuing commands.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Nov 30, 2010 1:00 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| You might also want to give some thought to not diagnosing & resolving problems by randomly issuing commands. |
I believe this topic was covered in the WMB Admin class. The instructor said something about shooting yourself in the foot. Perhaps our friend would do well to take that class?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| reshds |
| Posted: Tue Nov 30, 2010 2:10 pm Post subject: |
|
|
Apprentice
Joined: 25 Mar 2010
Posts: 37
Location: LA
|
Folks, Problem has been resolved after recreating the broker. Thanks all for your reply.
Vitor ,I would consider your suggestion.Thanks ! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 30, 2010 6:22 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| reshds wrote: |
Folks, Problem has been resolved after recreating the broker. Thanks all for your reply.
Vitor ,I would consider your suggestion.Thanks ! |
which problem?
The problem that your Broker didn't start up?
or the problem that you're doing things without proper training or learning? |
|
| Back to top |
|
|
|
|
