| Author |
Message
|
| WBI_User21 |
 Posted: Mon May 05, 2008 1:46 am Post subject: Broker and EG not running |
 |
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
Hello MB Experts,
Need your help in solving problem.
I want restart the broker. So I stopped the broker using
mqsistop brokername -i
then i started the broker using
mqsistart brokername
when i tried deploying the flows ..
an alert say that broker is not running
and eg is not running.
How can i resolve this problem
Following are details of os
Red Hat Linux
Message broker
BIPv600 en US POSIX
ucnv Console CCSID 1208 dft ucnv CCSID 1208
ICUW US-ASCII ICUA US-ASCII
BIP8996I: Version: 6001
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S600-L60322.2 DH600-L60313
BIP8999I: Build Type: Production
BIP8071I: Successful command completion.
thanks in advance |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon May 05, 2008 2:08 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
after deploying the bar file to the broker, did you get succesful acknowledgement back,
did you check the event logs
if not check that and let us know.
fire mqsilist <broker name> -e <exec group> and see does it displays the flow names or not..
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Mon May 05, 2008 2:50 am Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
After deploying i get following error
BIP1510E: Deployment failed; a deployment is already in progress to broker BKRK12
Nothing in the event logs
All flows and egs are in stopped
mqsilist brokername gives me following output
BIP8130I: Execution Group: EG4 - 0
BIP8130I: Execution Group: EG7 - 0
BIP8130I: Execution Group: EG3 - 0
BIP8130I: Execution Group: EG5 - 0
No dataflowengine.exe process is running in the os
any help ? |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Mon May 05, 2008 2:53 am Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
and command mqsilist <broker name> -e <exec group>
returns nothing
 |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Mon May 05, 2008 2:59 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
cancel the deployment and redeploy the file and see.
If that doesnt work, check the broker system logs to identify whats the problem.
verify if the broker got abended, if so raise PMR
hope the channels are running between configuration manager and broker
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 05, 2008 4:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you forced a broker to stop, while it was doing a deploy. That is what "-i" means, after all.
Now you don't appear to have the broker successfully started up again...
Before you can redo the deploy or cancel the deploy or see if the deploy failed, you need to get the broker running again.
Troubleshoot any errors in the runtime log that show up after you mqsistart...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Mon May 05, 2008 11:18 pm Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
thanks jeff for reply
i have checked logs in var/mqsi/user.log and /var/mqsi/common/errors
do i need to check any other logs... |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Mon May 05, 2008 11:25 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear WBI_User21,
I too faced a similar problem. But not sure how much in accordance to your problem. I checked the queue depth of the transmission queue (broker queue manager queue) in the Configuration Manager Queue Manager. Then I noticed tht the disconnect interval to the Sender channel from Config Manager QM to Broker QM was 6000 which is default. So ur Sender channel may be inactive. Then I cleared the transmission queue messages and the restarted the sender channel and then started the broker and then the deployed message flows successfuly. It worked for me. May be u can try it out.
To avoid this in future, change the disconnect interval to 0 of the sender channel
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Mon May 05, 2008 11:45 pm Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
thanks sri_csee1983...
i have checked these things. My broker and cm uses same qm.
thanks |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Tue May 06, 2008 12:07 am Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
Can anyone tell me the best place to look log in Solaris other than these
var/mqsi/user.log
/var/mqsi/common/errors
thanks in advance.. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Tue May 06, 2008 12:16 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Hmm.... Did u check after deleting the broker using mqsidelete is there any entry for tht broker in the table cbroker, cbrokerceg of the CM DB. if u have only one Broker, Just delete the contents in these table and try recreating it. Dont know how much it will help u. Just make a try if u still didnt get any solution.
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Tue May 06, 2008 12:18 am Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
| I cannot delete the broker. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue May 06, 2008 12:31 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| sri_csee1983 wrote: |
| Hmm.... Did u check after deleting the broker using mqsidelete is there any entry for tht broker in the table cbroker, cbrokerceg of the CM DB. if u have only one Broker, Just delete the contents in these table and try recreating it. |
Do not do this. If your Config Manager has a broker in a semi-deleted state, use the CMP API Exerciser to tidy it up. Never attempt to modify the CM's repository yourself; you're liable to screw up your whole domain.
WBI_User21, look in your OS system log for error details. Then when you've got your broker up and running, ensure that the broker's SYSTEM.BROKER.ADMIN.QUEUE is empty, then right click the broker in the toolkit and select the Cancel deployment option. Then try the original deployment again. |
|
| Back to top |
|
|
|
|
