| Author |
Message
|
| slaney |
 Posted: Wed Sep 08, 2004 2:29 am Post subject: Missing Broker - WBIMB 5.0 CSD03 |
 |
|
Novice
Joined: 24 Aug 2004
Posts: 14
Location: Alphacourt (Swindon UK)
|
This is a strange problem.... I have physically created a new broker domain i.e. a new configmgr and a single broker running on Solaris. I created the domain in the Toolkit. I have added the broker using the wizard that pops up when you right mouse click Broker Topology and go New -- > Broker . I successfully deployed the topology (using a FULL deploy) and got a successful response. However I can't see the broker in the Toolkit. I can re-deploy the topology and get messages from the broker indicating success but all I see is the icon for "Broker Topology" and nothing underneath. So I am unable to add any execution groups!
I am running WBIMB 5.0 with CSD03 on all boxes. My userId is a member of mqbrkrs and mqbrops.
How do I get the icon for the broker to show in the message brokers toolkit????
_________________
Steven Lane AMBCS
Information Security Consultant
Alphacourt Limited
http://www.alphacourt.com/html/services/securityserv/ |
|
| Back to top |
|
 |
| PGoodhart |
| Posted: Wed Sep 08, 2004 4:58 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
This is somewhat over simple but did you right click and connect to the configuration manager? I noticed you didn't say anything about connecting.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| slaney |
| Posted: Wed Sep 08, 2004 5:22 am Post subject: |
|
|
Novice
Joined: 24 Aug 2004
Posts: 14
Location: Alphacourt (Swindon UK)
|
 Sometimes I am dense and make a stupid mistake.  Sometimes I am stupid.  But I am not this stupid !!! However I really appreciate any suggestions otherwise I am going to delete and recreate everything. But surely this is a sledge hammer?
_________________
Steven Lane AMBCS
Information Security Consultant
Alphacourt Limited
http://www.alphacourt.com/html/services/securityserv/ |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Wed Sep 08, 2004 5:59 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Sorry, no offense, some of the posters are that stupid. 
I see you went through the other proper steps, which basically means you have a configuration problem, not operator error...
Is your broker running? Can you ping it? I had some issues with a firewall that resulted in something like what you discribed. (IP/Port blocking annoyance...)
Check your broker host name and port too, I had some issues with getting the host right. If it is localhost and 1414 that is the default (which won't work if the configuration manager is remote). If you are running your configuration manager locally you may not be allowing localhost and may need to enter an IP address instead. I had problems with the Host, as our DNS was insisting that abc.myserver.com and abc were two different machines on two different ip addresses.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| slaney |
| Posted: Wed Sep 08, 2004 7:07 am Post subject: |
|
|
Novice
Joined: 24 Aug 2004
Posts: 14
Location: Alphacourt (Swindon UK)
|
Hey.. no offense taken.
I don't think there is a firewall involved here. Anyway the underlying MQ transport is all working fine. I connect to the config mgr using the Message Brokers Toolkit for WebSphere Studio (hereafter called MBT) from the box that the configmgr is installed on. i.e the MBT is local to the config mgr. If I right mouse click the broker topology and do a deploy topology configuration ---> complete I get back from the broker three messages (indicating that comms were fine as MQ channels started etc):
| Code: |
BIP2056I: Broker BRK000001 successfully processed the entire internal configuration message.
An internal configuration message was processed to completion.
No user action required. |
followed by
| Code: |
BIP4045I: Configuration changed successfully.
The message broker received a configuration message and updated its configuration accordingly. This change concerned its publish-subscribe capability.
No user action required. |
The source of these messages is the broker (which is named!).
There is then a message from the config mgr:
| Code: |
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker BRK000001.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker BRK000001 was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker BRK000001. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center. |
Now this error also occurs in other broker domains and I have yet to fix it. It is also discussed extensively on this forum. On our other broker domains it makes no real impact on the perfmance of the config mgr, which does show the broker and does allow me to deploy BAR files.
Just to prove that the broker is properly deployed I tried to add it again and I get:
| Code: |
BIP1511E: Queue manager 'EAIHUB' cannot be associated with broker 'BRK000001'; it is already associated with broker 'BRK000001'.
An attempt was made to associate broker BRK000001 with WebSphere MQ queue manager EAIHUB, but broker BRK000001 already has this association. A WebSphere MQ queue manager can only have one broker associated with it.
Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker BRK000001 then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration from the real broker. It is only after all types of configuration data (message flows, message sets, topology, topics) have been successfully deleted from the real broker that the broker document is finally deleted from the configuration repository. Until that time the queue manager can not be associated with another broker. Once this has been done, you must also physically delete and recreate the real broker using the mqsideletebroker and mqsicreatebroker commands.
____________________________________________________________
BIP1711W: Broker is not accessible or does not exist.
An attempt was made to register for information on the Broker with UUID 'b91f85de-fe00-0000-0080-d51319f22e3a', but either the user who asked for the information does not have sufficient authority to do so or the Broker does not exist.
Ensure that the user of the application that issued the request has sufficient authority to view the Broker. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1711W: ExecutionGroup is not accessible or does not exist.
An attempt was made to register for information on the ExecutionGroup with UUID 'ba1f85de-fe00-0000-0080-d51319f22e3a', but either the user who asked for the information does not have sufficient authority to do so or the ExecutionGroup does not exist.
Ensure that the user of the application that issued the request has sufficient authority to view the ExecutionGroup. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1520I: Deploy operations successfully initiated.
The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: BRK000001 . Deleted brokers: .
Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker. |
Any reference to authority is not true since I have membership of mqbrkrs, mqbrops and I have also set mqsisetaclgroup:
| Code: |
BIP1778I: DOMAIN\slane - USER - F - BRK - UKBRKR1P_B
BIP1778I: wbi_admins - GROUP - F - RTS -
BIP1778I: DOMAIN\slane - USER - F - TOP -
BIP1778I: wbi_admins - GROUP - F - SUB -
BIP1778I: DOMAIN\slane - USER - F - EXE - UKBRKR1P_B\default
BIP1778I: wbi_admins - GROUP - F - TOP -
BIP1778I: DOMAIN\slane - USER - F - SUB -
BIP1778I: DOMAIN\slane - USER - F - RTS -
|
Note the names of groups, domain names etc above have been changed for obvious reasons...... but take it I am DOMAIN\slane and I am a member of the wbi_admins group.
The fact that the mqsilistaclgroup lists both the broker and the execution group default is further evidence that the config manager is aware of the broker. Otherwise it would not be possible to create acls for the object as they would not exist (and mqsicreateaclgroup returns an error).
My hunch.... there is something missing in a table of the config mgr. i.e. the database is corrupted. What do you reckon? Do the know the tables to look at to confirm or eliminate? If this is true what do I need to add? Or perhaps a gif file is missing from the config mgr install? Do you know where the config mgr might put some error messages such as "can't find xyz.gif"?
_________________
Steven Lane AMBCS
Information Security Consultant
Alphacourt Limited
http://www.alphacourt.com/html/services/securityserv/ |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Wed Sep 08, 2004 9:39 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Ah now it makes more sense... You definately have a DB problem.
Is this a broker that was upgraded from 2.x to 5?
Because if that is the case you need to do a uninstall and drop the database structure and then reinstall.
I had this kind of thing happen before and I was able to get it cleaned up by deleting rows out of the configuration manager database... but it was a bear to do. You basically have to find every entry in the database that is connected to that UID and delete it. It may be faster/safer to reinstall and drop the tables.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| slaney |
| Posted: Wed Sep 08, 2004 11:41 pm Post subject: |
|
|
Novice
Joined: 24 Aug 2004
Posts: 14
Location: Alphacourt (Swindon UK)
|
|
| Back to top |
|
|
|
|
