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 » WMBIMB 5.0 - problem with domain connection

Post new topic  Reply to topic
 WMBIMB 5.0 - problem with domain connection « View previous topic :: View next topic » 
Author Message
mq_pm
PostPosted: Wed Sep 15, 2004 12:19 pm    Post subject: WMBIMB 5.0 - problem with domain connection Reply with quote

Centurion

Joined: 27 Aug 2003
Posts: 132

Hi,

I have installed WMBIMB 5.0 on windows and was trying to work on it according to manuals. But initially itself it is giving a problem for me.

I have created required queuemanagers, databases, broker and configmgr with seperate queuemanagers. In the toolkit, first step is to create a domain, I was trying to create a domain giving the details of configmr, but iam getting an error and not able to create it.

BIP0889E: An exception occured while communicating with configuration manager on quemanger(XXXX). But queuemgr is correctly created, it is running and port.
I tried to create again configmgr , if there was any problem. but still same....not sure why iam i getting this error.

Error Details:

This report was generated by the 'main' thread.
This is not a thread instantiated by the Config Manager Proxy so
it is probably the main application thread that drives the API.
Problems here are usually caused by incorrect use of the API or
communication problems with the Config Manager... check the rest
of the report for more information.

The Config Manager Proxy detected the following exception:
com.ibm.broker.config.proxy.ConfigManagerProxyPropertyNotInitializedException: ConfigManagerProxy information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'administrator@mqhubt2' does not have authority to view the object. (UUID='', required attribute='name')
at com.ibm.broker.config.proxy.AdministeredObject.getProperty(Unknown Source)
at com.ibm.broker.config.proxy.AdministeredObject.getProperty(Unknown Source)
at com.ibm.broker.config.proxy.AdministeredObject.getName(Unknown Source)
at com.ibm.etools.mft.admin.model.AdministeredObjectAdapter.getName(Unknown Source)
at com.ibm.etools.mft.admin.model.AdministeredObjectAdapter.setEditedProperties(Unknown Source)
at com.ibm.etools.mft.admin.model.CMPAOModel.initEditedArtifact(Unknown Source)
at com.ibm.etools.mft.admin.ui.model.DomainModel.cmpConnectionChange(Unknown Source)
at com.ibm.etools.mft.admin.model.ArtifactCommandProcessor.cmpConnectionChange(Unknown Source)
at com.ibm.etools.mft.admin.model.AOAdapterControler.registerCMPConnectionListener(Unknown Source)
at com.ibm.etools.mft.admin.model.CMPAOModel.registerCMPConnectionListener(Unknown Source)
at com.ibm.etools.mft.admin.ui.model.DomainModel.registerCMPConnectionListener(Unknown Source)
at com.ibm.etools.mft.admin.ui.model.BAElementsModel.addDomainModel(Unknown Source)
at com.ibm.etools.mft.admin.wizards.domains.NewDomainWizard$1.run(Unknown Source)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:299)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:249)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:720)
at com.ibm.etools.mft.admin.wizards.domains.NewDomainWizard.saveParameters(Unknown Source)
at com.ibm.etools.mft.admin.wizards.domains.NewDomainWizard.performElementCreation(Unknown Source)
at com.ibm.etools.mft.admin.wizards.MBDAWizard.performFinish(Unknown Source)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:577)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:312)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:407)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:87)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code))
at org.eclipse.jface.window.Window.open(Window.java:542)
at org.eclipse.ui.internal.NewWizardShortcutAction.run(NewWizardShortcutAction.java:8
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:407)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:361)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:352)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:47)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code))
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)



ConfigManagerProxyPropertyNotInitializedException
is thrown when information on one of the objects maintained
by the Config Manager has not been supplied to the proxy, and
the proxy needs this information in order to complete an operation.
(For example, in order to create an execution group,
information on the owning broker must have been to supplied by the
Config Manager.)
Normally, the Config Manager will automatically supply this
information whenever a handle to the object is initialized, so
to receive this exception indicates a comms problem with the
Config Manager. Try restablishing the connection and retrying. If
the Config Manager Proxy is timing out as a result of a slow link
or a really large message, the period of time to wait before this
exception is thrown may need to be increased. See
ConfigManagerProxy.setRetryCharacteristics() for information on
how to do this.
Finally, here is the trace that led up to this exception getting thrown.
(Detailed trace, such as entry and exit information, is not included here.)

2004-09-15 16:03:46.0482 main........... i: com.ibm.broker.config.proxy.ConfigManagerProxyLogger instantiated
2004-09-15 16:04:11.0829 ModalContext... i: CMP sending:
DUMBLEDORE
serializer.version=1.0
commsmessage.type=com.ibm.broker.config.common.Request
...
commsmessage.operationtype=register
uuid=
commsmessage.configobjecttype=ConfigManagerProxy

2004-09-15 16:04:11.0999 ModalContext... i: MQSender successfully connected to MQHUBTC2
2004-09-15 16:04:12.0099 WMQI-CMP-MQRcvr i: MQReceiver successfully connected to MQHUBTC2
2004-09-15 16:04:50.0965 main........... com.ibm.broker.config.proxy.AdministeredObject.getProperty() threw an exception: ConfigManagerProxy information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'administrator@mqhubt2' does not have authority to view the object. (UUID='', required attribute='name'). Stack trace follows.
com.ibm.broker.config.proxy.ConfigManagerProxyPropertyNotInitializedException: ConfigManagerProxy information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'administrator@mqhubt2' does not have authority to view the object. (UUID='', required attribute='name')
at com.ibm.broker.config.proxy.AdministeredObject.getProperty(Unknown Source)
at com.ibm.broker.config.proxy.AdministeredObject.getProperty(Unknown Source)
at com.ibm.broker.config.proxy.AdministeredObject.getName(Unknown Source)
at com.ibm.etools.mft.admin.model.AdministeredObjectAdapter.getName(Unknown Source)
at com.ibm.etools.mft.admin.model.AdministeredObjectAdapter.setEditedProperties(Unknown Source)
at com.ibm.etools.mft.admin.model.CMPAOModel.initEditedArtifact(Unknown Source)
at com.ibm.etools.mft.admin.ui.model.DomainModel.cmpConnectionChange(Unknown Source)
at com.ibm.etools.mft.admin.model.ArtifactCommandProcessor.cmpConnectionChange(Unknown Source)
at com.ibm.etools.mft.admin.model.AOAdapterControler.registerCMPConnectionListener(Unknown Source)
at com.ibm.etools.mft.admin.model.CMPAOModel.registerCMPConnectionListener(Unknown Source)
at com.ibm.etools.mft.admin.ui.model.DomainModel.registerCMPConnectionListener(Unknown Source)
at com.ibm.etools.mft.admin.ui.model.BAElementsModel.addDomainModel(Unknown Source)
at com.ibm.etools.mft.admin.wizards.domains.NewDomainWizard$1.run(Unknown Source)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:299)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:249)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:720)
at com.ibm.etools.mft.admin.wizards.domains.NewDomainWizard.saveParameters(Unknown Source)
at com.ibm.etools.mft.admin.wizards.domains.NewDomainWizard.performElementCreation(Unknown Source)
at com.ibm.etools.mft.admin.wizards.MBDAWizard.performFinish(Unknown Source)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:577)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:312)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:407)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:87)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code))
at org.eclipse.jface.window.Window.open(Window.java:542)
at org.eclipse.ui.internal.NewWizardShortcutAction.run(NewWizardShortcutAction.java:8
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:407)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:361)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:352)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:47)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code))
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)


A maximum of the last 100 trace entries are shown here.
If more trace is required, attempt to reproduce the problem with the 'FileLogger' trace handler enabled.
To instantiate this, use the following method call to the Config Manager Proxy:
ConfigManagerProxy.setLogger("com.ibm.broker.config.proxy.FileLogger","myTraceFile.out");
where myTraceFile.out is the name of the trace file to which output should be directed.
Within the Eclipse environment, set the active logger to be the 'FileLogger', using
the WMQI Domain Administration preferences dialog.

End of Error Report.



If anyone can please let me know what problem it could be, it would of great help to me. Iam not able to figure out exactly to solve it. it is really very urgent. Thanks in advance.
Back to top
View user's profile Send private message Send e-mail
waugh
PostPosted: Wed Sep 15, 2004 12:27 pm    Post subject: Reply with quote

Master

Joined: 19 Feb 2004
Posts: 225

Hi PM,

what CSD level of WBIMB you are at? apply latest CSD's
is your current user member of mqm, other five WBIMB groups?
Back to top
View user's profile Send private message
mq_pm
PostPosted: Wed Sep 15, 2004 12:33 pm    Post subject: Reply with quote

Centurion

Joined: 27 Aug 2003
Posts: 132

I didn't apply any fix packs after installation . so it is at 0 level only.
The user is member of mqm and other grps.
Back to top
View user's profile Send private message Send e-mail
RocknRambo
PostPosted: Wed Sep 15, 2004 2:45 pm    Post subject: Reply with quote

Partisan

Joined: 24 Sep 2003
Posts: 355

Try after applying CSD, the current CSD level is 4,

and it is also suggested, not to open the Toolkit with out a CSD applied.
Back to top
View user's profile Send private message
kirani
PostPosted: Wed Sep 15, 2004 3:17 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

You need to have atlease CSD1 installed. Base product is not going to work without CSD.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
PGoodhart
PostPosted: Thu Sep 16, 2004 4:03 am    Post subject: Reply with quote

Master

Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA

Guys, Will it run at all now that they have started the broker at CSD 0? Or are they going to have to reinstall the broker?
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 16, 2004 5:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

If you are sure that you are at GA, and don't have a refreshed install media that is actually FixPack 1 or FixPack 2...

Then you will need to delete the broker, uninstall the software, reinstall the software and then apply at least FixPack 1.

This is documented in the readme or the install.html of FixPack 1.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMBIMB 5.0 - problem with domain connection
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.