| Author |
Message
|
| Devasis.Sahu |
 Posted: Tue Feb 08, 2005 2:27 am Post subject: Performance of Broker |
 |
|
Apprentice
Joined: 22 Feb 2003
Posts: 43
Location: India
|
Hi,
I am getting the following error when trying to deploy a simple message flow.
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker WBRK_BROKER.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRK_BROKER was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker WBRK_BROKER. 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.
------------------------------------------------------------------------------------
I have increased the heap size as well. but its not helping. Any idea how this can be tackled.
Dev |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Tue Feb 08, 2005 2:43 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
What has this to do with the subject? (Performance of Broker)
What do the error messages in system event log say? (have you looked at them?)
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| nathanw |
| Posted: Tue Feb 08, 2005 2:53 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
| also what platform are you runnig on |
|
| Back to top |
|
|
| Devasis.Sahu |
| Posted: Tue Feb 08, 2005 9:02 pm Post subject: Not able to deploy meg flow |
|
|
Apprentice
Joined: 22 Feb 2003
Posts: 43
Location: India
|
| I am using Win 2K platform. Since its taking 5-7 minutes for deploying a simple message flow, i had named in performance of broker. Anyways, has anybody faced this kind of problem. The log also doesnot tell anything significant. If you want i can do a post fo the Application log here if that helps. |
|
| Back to top |
|
|
| nathanw |
| Posted: Wed Feb 09, 2005 1:07 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
this is not a broker performance problme more like a problem in your set up etc
i nwould imagine the connections are timing out thus causing the long deploy time
I would rename this topic deploy delays or similar if i were you |
|
| Back to top |
|
|
| Devasis.Sahu |
| Posted: Wed Feb 09, 2005 3:45 am Post subject: |
|
|
Apprentice
Joined: 22 Feb 2003
Posts: 43
Location: India
|
Guys,
The problems seems to have been solved now. I deleted the broker and config manager and dropped the DB2 tables. Then recreated the entire setup. Its working fine now and very fast. I guess it was problem with some DB2 setup.
Thanx for your time.
Devasis |
|
| Back to top |
|
|
|
|
