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 » Unable to deploy second broker

Post new topic  Reply to topic
 Unable to deploy second broker « View previous topic :: View next topic » 
Author Message
lanny boy
PostPosted: Wed Nov 23, 2005 6:17 am    Post subject: Unable to deploy second broker Reply with quote

Voyager

Joined: 24 Nov 2003
Posts: 79
Location: UK

Hi,

I am using WBIMB CSD 04 on Windows/DB2 8 Fix Pack 8/MQ 5.3 CSD 9.

I am trying to create a second broker on a Windows platform. I have

created the broker
created the qm
created and verified the channels between config mgr and broker.

When i add the broker to my toolkit it adds but warns me that it is not started, even though i have successfully started it using mqsistart xxx.

When i go to deply the new broker nothing seems to happens. I get a message on the SYSTEM.BROKER.ADMIN.QUEUE as below
Quote:

<Broker label="BrokerName" uuid="03599cbc-0701-0000-0080-9be5a52f6a94" version="1">
<ControlGroup>
<DynamicSubscriptionEngine>
<Delete>
<AllNeighbours/>
</Delete>
</DynamicSubscriptionEngine>
</ControlGroup>
</Broker>

the deploy never times out but all subsequent attempts are refused because it says it is already deploying.

the user it runs under is an administrator, a member of mqm and all the mqbrkrs groups etc.

the only error i can see in the event log is as follows.
Quote:

( BrokerName ) Broker failed to create semaphore

An internal semaphore could not be created.

Use the system log messages to determine why the semaphore failed to be created. Contact your IBM support center if you are unable to resolve the problem.


Has anyone seen this before, or have any ideas why this is happening?

I should point out that i am attempting to completely partion both brokers as they will be running the same code but as DEV and a TEST envionment. To this end the broker DB for the second broker is contained in a seperate DB instance to the first broker and the config mgr.

Thanks!
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 23, 2005 6:22 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Is there a BIP number with that error?

If you created the broker first, it would have created the qm for you. So I'm assuming you created the qm first.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
lanny boy
PostPosted: Wed Nov 23, 2005 6:31 am    Post subject: Reply with quote

Voyager

Joined: 24 Nov 2003
Posts: 79
Location: UK

thanks for your quick reply Jeff

I have tried it a few times and in this last case i issued the mqsicreate broker first, so it automatically created the qm for me.

The BIP number from the event viewer is BIPv500
EVENT ID = 2818 (not sure if that is relevant)
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 23, 2005 6:32 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

BIPv500 is just the system version number.

There should be something in the text of the message that is a BIPXXXX number, probably right before where it says (Broker Name).
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Wed Nov 23, 2005 6:33 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

This will be BIP2818; this usually means that the broker could not create a system-wide mutex that it requires.

First, try checking the authority of the broker's userid's primary group (e.g. try making it mqm).

I'd also suggest raising a PMR.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 23, 2005 6:41 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

mqmatt wrote:
This will be BIP2818

While I really appreciate the bip search number function in the broker Info Center, it would also be nice to have a browseable list of the available BIPS.

Also, holy cow! The Troubleshooting guide for broker v6 includes a reference to MQSeries.net!
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
lanny boy
PostPosted: Wed Nov 23, 2005 6:45 am    Post subject: Reply with quote

Voyager

Joined: 24 Nov 2003
Posts: 79
Location: UK

Hi,

there is no mention of BIP2818 in the event guide....

the user is already a member of mqm.

Looks like a PMR!

thanks for your help, i'll post the PMR results when i get them.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Wed Nov 23, 2005 7:33 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

jefflowrey wrote:
While I really appreciate the bip search number function in the broker Info Center, it would also be nice to have a browseable list of the available BIPS.

Understood. At present, I just load up BIPv600.properties (or whatever) from the messages directory and do a text search.


jefflowrey wrote:
Also, holy cow! The Troubleshooting guide for broker v6 includes a reference to MQSeries.net!


Hehe - the fame spreads wider
Note that the site's also linked in the toolkit: Help -> Welcome -> Web Resources -> Getting Involved

-Matt
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 23, 2005 7:35 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

mqmatt wrote:
Understood. At present, I just load up BIPv600.properties (or whatever) from the messages directory and do a text search.


Which only works if you have local install...
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
mgk
PostPosted: Wed Nov 23, 2005 8:11 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Hi,

I have just reproduced this. It is a defect, and you should raise a PMR for a proper fix. However, I believe there is a workaround. This scenario should only happen on windows and only when the two brokers are run under seperate user ID's. E.g., maybe one of them has been set to run under the SYSTEM account in order to "interact with the desktop" and the second broker has not. Try running both brokers under the same user ID.

Regards,


MGK
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
solomita
PostPosted: Thu Dec 22, 2005 11:21 am    Post subject: Reply with quote

Voyager

Joined: 06 May 2003
Posts: 94

I am having a similar problem on Linux. I have created a default broker/configmgr using the toolkit and now tried to create a new broker. I have succesfully created the broker, dbases and have chls runnign between my new broker and the config mgr. HOwever, even though the broker is running, the toolkit says otherwise. They were created with the same ids except the dbase of my new broker was done under a different id. Any ideas?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5
Back to top
View user's profile Send private message Yahoo Messenger
mqmatt
PostPosted: Thu Dec 22, 2005 3:44 pm    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

solomita wrote:
I am having a similar problem on Linux. I have created a default broker/configmgr using the toolkit and now tried to create a new broker. I have succesfully created the broker, dbases and have chls runnign between my new broker and the config mgr. HOwever, even though the broker is running, the toolkit says otherwise. They were created with the same ids except the dbase of my new broker was done under a different id. Any ideas?


Look in the event log editor in the toolkit, and in the Linux system log; are there any errors reported?
Back to top
View user's profile Send private message
solomita
PostPosted: Thu Dec 22, 2005 7:35 pm    Post subject: Reply with quote

Voyager

Joined: 06 May 2003
Posts: 94

there is no error in the toolkit but if i try to redeploy it says its still waiting for a response back. I cant remember where the error logs are....can you help out there?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5
Back to top
View user's profile Send private message Yahoo Messenger
lckwj
PostPosted: Wed May 09, 2007 3:41 am    Post subject: Reply with quote

Novice

Joined: 24 May 2006
Posts: 12

did anyone ever get a resolution to this ?
I am having the same issue running 2 brokers on a single Windows box (XP) when they run a 2 different users. I can run 2 brokers under the same user id fine.

I am using V6.0.3
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed May 09, 2007 3:59 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Make sure the second broker is really started and has no error messages in the error log like 'could not connect to database' and such... because with that kind of error the bip process will be running but not much anything else and the broker is not functional....

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unable to deploy second broker
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.