| Author |
Message
|
| vam |
 Posted: Tue Aug 23, 2011 7:29 am Post subject: MB Issue |
 |
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Hello MQSeries Team,
I was unable stop the flows in TESTD server after some server move even after issuing stop command/terminating the processs/bouncing the broker.
Could you please advice me ? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Aug 23, 2011 7:34 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
What platform, what version. On Unix variants, you have to be sudo'd to the same UserId as the UserId that started the Broker.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| vam |
| Posted: Tue Aug 23, 2011 7:39 am Post subject: MB Issue |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Its UNIX OS.
I am having all the permissions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 23, 2011 7:39 am Post subject: Re: MB Issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vam wrote: |
| Hello MQSeries Team |
We're not a team. We're a bunch of slightly scruffy volunteers. It's kind of you to say that, but don't invest us with more than we are.
We're certainly not The MQSeries Team in any IBM sense of the word. You talk to them in an entirely different way.
(Though there is some overlap....)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Aug 23, 2011 8:35 am Post subject: Re: MB Issue |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| vam wrote: |
Its UNIX OS.
I am having all the permissions. |
Thats not what I said.
The Broker runtime is started under a certain Id. If this Id = A and you are Id B, you cannot stop the Broker.
Its not a permissions issue. You can be root and it still wont stop the Broker.
You have to sudo to Id A to issue the stop command.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 23, 2011 8:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Define "unable to stop the flows".
You said you bounced the broker. What happened? Did all of the existing DFE processes end and then start up again?
Is there, perhaps through some amazing magic, a set of error messages in the system log that might indicate the actual problem? |
|
| Back to top |
|
|
| vam |
| Posted: Tue Aug 23, 2011 9:31 am Post subject: MB Issue |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Later all the flows got started up fine,but I was unable to stop the flows.
Tried to start using command prompt,but it didn't workout.
LOG:
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1028I: Submitting request to the Configuration Manager to stop 'TESTD/BUY/SUB_FLOW...
BIP1029I: Waiting up to 60 second(s) for broker TESTDto update its configuration...
BIP1021E: Message flow SUB_FLOWcould not be stopped.
The utility was asked to stop message flow SUB_FLOW running in execution group BUY on broker TESTD, but the action didnot complete successfully.
Ensure that the broker TESTD. and the Configuration Manager are running and that the current user has the authority defined in the Configuration Manager to control message flows on that execution group. If you suspect that the run state is not being reported correctly, try redeploying the topology using the 'complete' option. If the problem persists, contact your IBM support representative. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Aug 23, 2011 9:35 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
This result happens because the user id trying to stop the flows or stop the broker is not the same as the service id that the broker is running on. This is a characteristic of WMB Unix runtime. The User id issuing the stop command, whether for flows or for the whole broker, must be the same user id that started the broker in the first place. It is not enough that you have the right permissions, it must be the same exact id. Sudo works.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 23, 2011 9:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| This result happens because the user id trying to stop the flows or stop the broker is not the same as the service id that the broker is running on. This is a characteristic of WMB Unix runtime. The User id issuing the stop command, whether for flows or for the whole broker, must be the same user id that started the broker in the first place. It is not enough that you have the right permissions, it must be the same exact id. Sudo works. |
Or it happens because the flows are stuck in loops taking a long time to respond to any request for action. Or that the configmgr's qmgr is not able to talk to the broker's queue manager, or any number of other things.
Please note very carefully that this was a report of a conversation with the configmgr, which does not have anything to do with sudo or actually stopping the broker itself.
it also indicates that we are dealing with version 6.1 or older - hopefully not older, as everything older than 6.1 is out of support. |
|
| Back to top |
|
|
|
|
