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 » stopping message broker issue

Post new topic  Reply to topic
 stopping message broker issue « View previous topic :: View next topic » 
Author Message
Sue_2828
PostPosted: Mon Feb 16, 2009 12:05 pm    Post subject: stopping message broker issue Reply with quote

Apprentice

Joined: 14 Feb 2009
Posts: 37

Hi guys.
I am having an issue but can't determine the cause. On an AIX environment when I start the broker from the command line :

mqsistart mybroker

I can see the queue manager starting with no issue , however, I don't get any message indicating the broker is started , at the same time no errors at the prompt.

I can then start the configuration manager fine from the command line , I can also see it running .

However when I then try to stop the message broker , I get the following :
>mqsistop mybroker
BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted.

That's the only place where I can see the broker wasn't started or is having an issue , how can I troubleshoot this ? can you please advice ?
Back to top
View user's profile Send private message
bloomy
PostPosted: Mon Feb 16, 2009 12:28 pm    Post subject: Reply with quote

Acolyte

Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA

Is this a new broker, or you are having this problem on an existing broker. To be more specific did this broker run at all previously.

If you want to check if your broker is running or started after you issued a mqsistart <brokername>

Try any two of the below to see if the broker is running.

1. Do a ps -ef|grep bip

output should be when all the broker services are running:
svcwbimb 598170 1 0 11:37:52 pts/3 0:00 bipservice CMGR
svcwbimb 643182 1511544 0 Feb 14 - 7:06 biphttplistener BRK
svcwbimb 1470630 1 0 Feb 14 - 0:00 bipservice BRK
svcwbimb 1511544 1470630 0 Feb 14 - 0:07 bipbroker BRK

svcwbimb 1679380 598170 24 11:37:53 pts/3 38:25 bipconfigmgr CMGR

the higlighted services are for broker, they should show up if the broker is running.

2. check for the syslogs after you start the broker to see the following mesage

Feb 11 15:05:12 localhost user:info WebSphere Broker v6102[1634382]: (BRK)[1]BIP8873I: Starting the component verification for component 'BRK'. : BRK.mqsistart: /build/S610_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 74: ImbComponentVerification::verify: :

If you cannot see the broker services running, try seeing the syslogs to see what caused a start to fail.
Back to top
View user's profile Send private message
Sue_2828
PostPosted: Mon Feb 16, 2009 12:46 pm    Post subject: Reply with quote

Apprentice

Joined: 14 Feb 2009
Posts: 37

Yes this is a new broker , and never started before . There are no flows on there. After doing "ps -ef|grep bip" I can see the config manager starting but not the broker . How do I check the syslogs or troubleshoot it from here . I am also new to broker , please advice . thanks
Back to top
View user's profile Send private message
bloomy
PostPosted: Mon Feb 16, 2009 1:10 pm    Post subject: Reply with quote

Acolyte

Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA

Configuring your syslogs is explained in the below link. you can redirect your syslogs to a new directory which is owned by the broker user id, so that you need not to have root access every time you may want to check the error logs.

try configuring this, try a start again, check for the error logs, I am sure there will be some information there as why did not the broker startup.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp
Back to top
View user's profile Send private message
bloomy
PostPosted: Mon Feb 16, 2009 1:16 pm    Post subject: Reply with quote

Acolyte

Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA

Type syslogs in the search, that will lead you to configuring syslog steps.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Feb 16, 2009 1:23 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Broker doesn't "run" until at least one flow has been deployed to at least one ExecutionGroup.

You should see a line or two in the syslogs that says that mqsistart has done something, but you won't see more than two, and they won't tell you much.

Once you create an EG and deploy a simple flow (I ususally do MQinput->MQoutput), then you will see that the EG starts up and you should see an Open Input Count on the MQInput node's queue.
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 » stopping message broker issue
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.