| Author |
Message
|
| Zappa |
 Posted: Thu Nov 17, 2005 8:00 am Post subject: WMB V6 broker running but toolkit says its not |
 |
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
| I've setup a WMB V6 broker and configmgr on the same server, both appear to have started and share the same qmgr running on AIX. The toolkit running on windows connects to the configmgr OK - broker domain is displayed. From the toolkit I create the broker using same name and qmgr as setup on the AIX box but two alerts appear, saying the broker and execution group aren't running. The qmgr has a message on the SYSTEM.BROKER.ADMIN.QUEUE. What log do I need to read and what might I have missed? |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu Nov 17, 2005 8:08 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Looks like either the broker isn't running (check the system log) or you just haven't deployed anything to the broker yet.
The broker will appear as 'not running' until you've actually successfully deployed to it; not until this happens does the broker starts sending status messages to the Config Manager.
-Matt |
|
| Back to top |
|
|
| Zappa |
| Posted: Fri Nov 18, 2005 12:32 am Post subject: |
|
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
| I issued the delta deploy from the toolkit, from the syslog I see the WMB service starting followed by integrity check failures regarding a number of columns missing from the database even though there were no errors when the broker was initially created. The service process is still running but when and how do these columns get created? |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Nov 18, 2005 4:41 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
The database tables are created when you create the broker; did you see any errors when you ran mqsicreatebroker?
What DB are you running? |
|
| Back to top |
|
|
| Zappa |
| Posted: Fri Nov 18, 2005 5:43 am Post subject: |
|
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
I'm running Oracle 9.2 and there weren't any errors during creation. I read that a version WMB 6 broker can share a MQSI 2.1 broker database. But I'm starting to think that this is the issue judging by the missing column errors in the odbc trace...
 |
|
| Back to top |
|
|
| JT |
| Posted: Fri Nov 18, 2005 6:47 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| I read that a version WMB 6 broker can share a MQSI 2.1 broker database. |
| The V6.0 Information Center wrote: |
There are some conditions for a Version 2.1 broker to participate in a WebSphere Message Broker Version 6.0 broker domain:- A Version 2.1 broker and a Version 6.0 broker must use separate sets of database tables. This means that, if a Version 2.1 broker and a Version 6.0 broker share a database, they must use different database schemas.
|
|
|
| Back to top |
|
|
| ashritha |
| Posted: Fri Nov 18, 2005 12:48 pm Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
Hi,
I do not know if this issue is already closed. But, the answer possible is.....
For the first time when you add your broker to the Broker Topology in the Domains view of the toolkit, 2 alerts as you mentioned are always seen. But once you deploy something on it successfully, you will no longer see those alerts.
Everytime you have a new execution group or new beoker added you see these alerts until something is deployed successfully on them. |
|
| Back to top |
|
|
| Zappa |
| Posted: Mon Nov 21, 2005 1:40 am Post subject: |
|
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
The deployment fails - the problem was the database. I was creating the broker with the same user/pswd and database that the version 2.1 broker was created with i.e. no new schema.
I've got our DBA to create a brand new DB and recreated the V6 broker using that i.e. not sharing the V2.1 DB
Broker creation works - followed by and a successful deployment from the toolkit - no errors in the syslog or ODBC trace.
Problems were all down to me trying to share the V2.1 DB without a new schema - (wot a numpty)
Thanks for your help guys.....
 |
|
| Back to top |
|
|
|
|
