Joined: 09 Oct 2006 Posts: 22 Location: Stockholm, Sweden
Blomman wrote:
Problem solved!
Somehow the CFGmanager and WMB got different UUIDs.....
I recreated the broker and now it works fine.
Txh for the input.
Regards!
//Michael
Sorry if this is a bit late in the discussion but did you try to adopt the broker using the Configuration Manager Proxy API Excerciser?
Quote:
In previous releases of WebSphere Message Broker if a broker became orphaned from its Configuration Manager it was not possible to connect it to a new Configuration Manager. In WebSphere Message Broker V6.1 this limitation has been removed. It is now possible to associate an existing broker with a specific Configuration Manager. A broker can only be associated with one configuration manager at a time and it is not recommended to use this adopt a broker facility to migrate a broker from development all the way to production by simply changing the configuration manager that it is associated with.
To adopt a broker, use the adoptBroker method of the TopologyProxy class (TopologyProxy.adoptBroker()). This nethod requests that a new configuration manager take over management of a broker previously managed by another configuration manager. You can use the Configuration Manager Proxy (CMP) API Exerciser sample for guidance here. When adopting a broker in this way, the state in the run-time broker supersedes any information in the configuration manager.
Somehow the CFGmanager and WMB got different UUIDs.....
I recreated the broker and now it works fine.
Txh for the input.
Regards!
//Michael
Sorry if this is a bit late in the discussion but did you try to adopt the broker using the Configuration Manager Proxy API Excerciser?
Quote:
In previous releases of WebSphere Message Broker if a broker became orphaned from its Configuration Manager it was not possible to connect it to a new Configuration Manager. In WebSphere Message Broker V6.1 this limitation has been removed. It is now possible to associate an existing broker with a specific Configuration Manager. A broker can only be associated with one configuration manager at a time and it is not recommended to use this adopt a broker facility to migrate a broker from development all the way to production by simply changing the configuration manager that it is associated with.
To adopt a broker, use the adoptBroker method of the TopologyProxy class (TopologyProxy.adoptBroker()). This nethod requests that a new configuration manager take over management of a broker previously managed by another configuration manager. You can use the Configuration Manager Proxy (CMP) API Exerciser sample for guidance here. When adopting a broker in this way, the state in the run-time broker supersedes any information in the configuration manager.
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