MQSeries.net :: View topic - broker domain not created in the toolkit

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » broker domain not created in the toolkit

broker domain not created in the toolkit

« View previous topic :: View next topic »

Author

Message

mrgate

Posted: Wed Apr 25, 2007 5:51 am Post subject: broker domain not created in the toolkit

Centurion

Joined: 28 Feb 2007
Posts: 141
Location: India

Hi guys,
I have uninstalled default configuration manager,
default broker and default database and have created a custom
database, custom broker and custom confifuration manager along
with queue manager in mq. now what is the problem is that I am
trying to create the broker domain in toolkit. In the first step I have
given the queue manager name and listener port number and
entered next so that it is going to create the broker domain.

It is not creating and is giving the error as :
The queue manager 'BROKERMANAGER' is either not running, or a Configuration Manager has not been defined on it
(MQ reason code 2009 while trying to connect).

I have started all the services and the listener port nomber. can any one help me in solving this problem.

marcin.kasinski

Posted: Wed Apr 25, 2007 6:09 am Post subject: Re: broker domain not created in the toolkit

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

... and name of QM of your config manager is BROKERMANAGER ?

In doman configuration you specify parameters of config manager.
_________________
Marcin

mrgate

Posted: Wed Apr 25, 2007 6:17 am Post subject: Re: broker domain not created in the toolkit

Centurion

Joined: 28 Feb 2007
Posts: 141
Location: India

marcin.kasinski wrote:

... and name of QM of your config manager is BROKERMANAGER ?

In doman configuration you specify parameters of config manager.

yes I have specified the parameters of configuration manager like port no:5000 and host:localhost but still not working.

marcin.kasinski

Posted: Wed Apr 25, 2007 6:18 am Post subject: Re: broker domain not created in the toolkit

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

rock wrote:

marcin.kasinski wrote:

... and name of QM of your config manager is BROKERMANAGER ?

In doman configuration you specify parameters of config manager.

yes I have specified the parameters of configuration manager like port no:5000 and host:localhost but still not working.

Have you red logs of this QM ?
_________________
Marcin

mrgate

Posted: Wed Apr 25, 2007 6:22 am Post subject: Re: broker domain not created in the toolkit

Centurion

Joined: 28 Feb 2007
Posts: 141
Location: India

marcin.kasinski wrote:

rock wrote:

marcin.kasinski wrote:

... and name of QM of your config manager is BROKERMANAGER ?

In doman configuration you specify parameters of config manager.

yes I have specified the parameters of configuration manager like port no:5000 and host:localhost but still not working.

Have you red logs of this QM ?

yes but no result. the output of log file is:

!SESSION Apr 24, 2007 21:53:07.281 ---------------------------------------------
eclipse.buildId=I200406192000
java.fullversion=J2RE 1.4.2 IBM J9 2.2 Windows 2000 x86-32 j9n142-20040917 (JIT enabled)
J9VM - 20040916_0908_lHdSMR
JIT - r7_level20040915_1801
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -plugincustomization C:\Program Files\IBM\MessageBrokersToolkit\6.0\eclipse\plugins\com.ibm.etools.msgbroker.tooling_6.0.0\plugin_customization.ini

!ENTRY org.eclipse.help 4 0 Apr 24, 2007 21:53:07.281
!MESSAGE Error occurred processing file toc.xml.
!STACK 0
java.lang.RuntimeException: toc label==null
at org.eclipse.help.internal.toc.Toc.<init>(Unknown Source)
at org.eclipse.help.internal.toc.TocFileParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.help.internal.toc.TocFileParser.parse(Unknown Source)
at org.eclipse.help.internal.toc.TocBuilder.buildTocFile(Unknown Source)
at org.eclipse.help.internal.toc.TocFile.build(Unknown Source)
at org.eclipse.help.internal.toc.TocBuilder.build(Unknown Source)
at org.eclipse.help.internal.toc.TocManager.build(Unknown Source)
at org.eclipse.help.internal.toc.TocManager.<init>(Unknown Source)
at org.eclipse.help.internal.HelpPlugin.getTocManager(Unknown Source)
at org.eclipse.help.internal.base.HelpDisplay.displayHelpResource(Unknown Source)
at org.eclipse.help.ui.internal.DefaultHelpUI.displayHelpResource(Unknown Source)
at org.eclipse.ui.help.WorkbenchHelp.displayHelpResource(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.showHelpTopic(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.doExecute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.access$0(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.execute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(Unknown Source)
at org.eclipse.swt.browser.Browser$3.handleEvent(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventTable.sendEvent(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.notifyListener(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.Invoke(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.access$1(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink$1.method6(Unknown Source)
at org.eclipse.swt.internal.ole.win32.COMObject.callback6(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)

!ENTRY org.eclipse.core.runtime 4 2 Apr 25, 2007 02:24:11.93
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.runtime".
!STACK 0
java.lang.NullPointerException
at com.ibm.etools.mft.admin.model.BAWorkbenchModel.reset(Unknown Source)
at com.ibm.etools.mft.admin.model.BAWorkbenchModel.reset(Unknown Source)
at com.ibm.etools.mft.admin.ui.workbenchpart.AdminGraphicalEditor.dispose(Unknown Source)
at com.ibm.etools.mft.admin.topology.ui.TopologyEditor.dispose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPartReference.dispose(Unknown Source)
at org.eclipse.ui.internal.EditorManager$Editor.dispose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage$5.run(Unknown Source)
at org.eclipse.core.internal.runtime.InternalPlatform.run(Unknown Source)
at org.eclipse.core.runtime.Platform.run(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.disposePart(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.closeEditors(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.closeAllEditors(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.dispose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.hardClose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.busyClose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.access$0(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.close(Unknown Source)
at org.eclipse.jface.window.WindowManager.close(Unknown Source)
at org.eclipse.ui.internal.Workbench$10.run(Unknown Source)
at org.eclipse.core.internal.runtime.InternalPlatform.run(Unknown Source)
at org.eclipse.core.runtime.Platform.run(Unknown Source)
at org.eclipse.ui.internal.Workbench.busyClose(Unknown Source)
at org.eclipse.ui.internal.Workbench.access$8(Unknown Source)
at org.eclipse.ui.internal.Workbench$12.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.Workbench.close(Unknown Source)
at org.eclipse.ui.internal.Workbench.close(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.busyClose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.access$0(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.close(Unknown Source)
at org.eclipse.jface.window.Window.handleShellCloseEvent(Unknown Source)
at org.eclipse.jface.window.Window$2.shellClosed(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Unknown Source)
at org.eclipse.swt.widgets.Control.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Decorations.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Shell.callWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Control.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Decorations.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Shell.callWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Control.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Decorations.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)
!SESSION Apr 25, 2007 02:24:55.828 ---------------------------------------------
eclipse.buildId=I200406192000
java.fullversion=J2RE 1.4.2 IBM J9 2.2 Windows 2000 x86-32 j9n142-20040917 (JIT enabled)
J9VM - 20040916_0908_lHdSMR
JIT - r7_level20040915_1801
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -plugincustomization C:\Program Files\IBM\MessageBrokersToolkit\6.0\eclipse\plugins\com.ibm.etools.msgbroker.tooling_6.0.0\plugin_customization.ini

!ENTRY org.eclipse.help 4 0 Apr 25, 2007 02:24:55.828
!MESSAGE Error occurred processing file toc.xml.
!STACK 0
java.lang.RuntimeException: toc label==null
at org.eclipse.help.internal.toc.Toc.<init>(Unknown Source)
at org.eclipse.help.internal.toc.TocFileParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.help.internal.toc.TocFileParser.parse(Unknown Source)
at org.eclipse.help.internal.toc.TocBuilder.buildTocFile(Unknown Source)
at org.eclipse.help.internal.toc.TocFile.build(Unknown Source)
at org.eclipse.help.internal.toc.TocBuilder.build(Unknown Source)
at org.eclipse.help.internal.toc.TocManager.build(Unknown Source)
at org.eclipse.help.internal.toc.TocManager.<init>(Unknown Source)
at org.eclipse.help.internal.HelpPlugin.getTocManager(Unknown Source)
at org.eclipse.help.internal.base.HelpDisplay.displayHelpResource(Unknown Source)
at org.eclipse.help.ui.internal.DefaultHelpUI.displayHelpResource(Unknown Source)
at org.eclipse.ui.help.WorkbenchHelp.displayHelpResource(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.showHelpTopic(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.doExecute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.access$0(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.execute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(Unknown Source)
at org.eclipse.swt.browser.Browser$3.handleEvent(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventTable.sendEvent(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.notifyListener(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.Invoke(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.access$1(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink$1.method6(Unknown Source)
at org.eclipse.swt.internal.ole.win32.COMObject.callback6(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)

!ENTRY org.eclipse.core.runtime 4 2 Apr 25, 2007 02:50:14.328
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.runtime".
!STACK 0
java.lang.NullPointerException
at com.ibm.etools.mft.admin.model.BAWorkbenchModel.reset(Unknown Source)
at com.ibm.etools.mft.admin.model.BAWorkbenchModel.reset(Unknown Source)
at com.ibm.etools.mft.admin.ui.workbenchpart.AdminGraphicalEditor.dispose(Unknown Source)
at com.ibm.etools.mft.admin.topology.ui.TopologyEditor.dispose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPartReference.dispose(Unknown Source)
at org.eclipse.ui.internal.EditorManager$Editor.dispose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage$5.run(Unknown Source)
at org.eclipse.core.internal.runtime.InternalPlatform.run(Unknown Source)
at org.eclipse.core.runtime.Platform.run(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.disposePart(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.closeEditors(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.closeAllEditors(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.dispose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.hardClose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.busyClose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.access$0(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.close(Unknown Source)
at org.eclipse.jface.window.WindowManager.close(Unknown Source)
at org.eclipse.ui.internal.Workbench$10.run(Unknown Source)
at org.eclipse.core.internal.runtime.InternalPlatform.run(Unknown Source)
at org.eclipse.core.runtime.Platform.run(Unknown Source)
at org.eclipse.ui.internal.Workbench.busyClose(Unknown Source)
at org.eclipse.ui.internal.Workbench.access$8(Unknown Source)
at org.eclipse.ui.internal.Workbench$12.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.Workbench.close(Unknown Source)
at org.eclipse.ui.internal.Workbench.close(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.busyClose(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.access$0(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.close(Unknown Source)
at org.eclipse.jface.window.Window.handleShellCloseEvent(Unknown Source)
at org.eclipse.jface.window.Window$2.shellClosed(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Unknown Source)
at org.eclipse.swt.widgets.Control.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Decorations.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Shell.callWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Control.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Decorations.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Shell.callWindowProc(Unknown Source)
at org.eclipse.swt.widgets.Control.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Decorations.windowProc(Unknown Source)
at org.eclipse.swt.widgets.Display.windowProc(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)
!SESSION Apr 25, 2007 18:30:05.140 ---------------------------------------------
eclipse.buildId=I200406192000
java.fullversion=J2RE 1.4.2 IBM J9 2.2 Windows 2000 x86-32 j9n142-20040917 (JIT enabled)
J9VM - 20040916_0908_lHdSMR
JIT - r7_level20040915_1801
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -plugincustomization C:\Program Files\IBM\MessageBrokersToolkit\6.0\eclipse\plugins\com.ibm.etools.msgbroker.tooling_6.0.0\plugin_customization.ini

!ENTRY org.eclipse.help 4 0 Apr 25, 2007 18:30:05.140
!MESSAGE Error occurred processing file toc.xml.
!STACK 0
java.lang.RuntimeException: toc label==null
at org.eclipse.help.internal.toc.Toc.<init>(Unknown Source)
at org.eclipse.help.internal.toc.TocFileParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.help.internal.toc.TocFileParser.parse(Unknown Source)
at org.eclipse.help.internal.toc.TocBuilder.buildTocFile(Unknown Source)
at org.eclipse.help.internal.toc.TocFile.build(Unknown Source)
at org.eclipse.help.internal.toc.TocBuilder.build(Unknown Source)
at org.eclipse.help.internal.toc.TocManager.build(Unknown Source)
at org.eclipse.help.internal.toc.TocManager.<init>(Unknown Source)
at org.eclipse.help.internal.HelpPlugin.getTocManager(Unknown Source)
at org.eclipse.help.internal.base.HelpDisplay.displayHelpResource(Unknown Source)
at org.eclipse.help.ui.internal.DefaultHelpUI.displayHelpResource(Unknown Source)
at org.eclipse.ui.help.WorkbenchHelp.displayHelpResource(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.showHelpTopic(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.doExecute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.access$0(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.execute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(Unknown Source)
at org.eclipse.swt.browser.Browser$3.handleEvent(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventTable.sendEvent(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.notifyListener(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.Invoke(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink.access$1(Unknown Source)
at org.eclipse.swt.ole.win32.OleEventSink$1.method6(Unknown Source)
at org.eclipse.swt.internal.ole.win32.COMObject.callback6(Unknown Source)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5

marcin.kasinski

Posted: Wed Apr 25, 2007 6:24 am Post subject: Re: broker domain not created in the toolkit

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

I'm talking about queue manager logs.

You can not connect to config manager queue manager ( 'BROKERMANAGER').

In this logs you will find why.
_________________
Marcin

mrgate

Posted: Wed Apr 25, 2007 6:30 am Post subject: Re: broker domain not created in the toolkit

Centurion

Joined: 28 Feb 2007
Posts: 141
Location: India

marcin.kasinski wrote:

I'm talking about queue manager logs.

You can not connect to config manager queue manager.

In this logs you will find why.

qmanagers log is:

04/25/2007 18:40:21
AMQ8003: WebSphere MQ queue manager 'BROKERMANAGER' started.

EXPLANATION:
WebSphere MQ queue manager 'BROKERMANAGER' started.
ACTION:
None.
-------------------------------------------------------------------------------
04/25/2007 18:40:24
AMQ8048: Default objects statistics : 31 created. 0 replaced. 0 failed.

EXPLANATION:
Information on the number of objects created or replaced successfully as well
as any failures that occurred while creating the default objects.
ACTION:
None.
-------------------------------------------------------------------------------
04/25/2007 18:40:27
AMQ8004: WebSphere MQ queue manager 'BROKERMANAGER' ended.

EXPLANATION:
WebSphere MQ queue manager 'BROKERMANAGER' ended.
ACTION:
None.
-------------------------------------------------------------------------------
04/25/2007 18:40:31
AMQ8003: WebSphere MQ queue manager 'BROKERMANAGER' started.

EXPLANATION:
WebSphere MQ queue manager 'BROKERMANAGER' started.
ACTION:
None.
-------------------------------------------------------------------------------
04/25/2007 18:40:31
AMQ9410: Repository manager started

EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
04/25/2007 19:27:29
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:27:29
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:27:39
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:27:39
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:27:49
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:27:49
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:27:59
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:27:59
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:28:09
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:28:09
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:28:19
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:28:19
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:31:18
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:31:18
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:31:28
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:31:28
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:31:38
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:31:38
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:31:48
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:31:48
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:31:58
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:31:58
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:32:08
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:32:08
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:35:17
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:35:17
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:35:27
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:35:27
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:35:37
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:35:37
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:35:47
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:35:47
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:35:57
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:35:57
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:36:07
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:36:07
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:53:48
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:53:48
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:53:58
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:53:58
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:54:08
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:54:08
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:54:18
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:54:18
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:54:28
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:54:28
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:54:38
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:54:38
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:59:20
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:59:20
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:59:30
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:59:30
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:59:40
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:59:40
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 19:59:50
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 19:59:50
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:00:00
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:00:00
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:00:10
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:00:10
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:03:19
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:03:19
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:03:29
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:03:29
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:03:39
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:03:39
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:03:49
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:03:49
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:03:59
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:04:00
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:04:10
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:04:10
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:13:12
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:13:12
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:13:22
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:13:23
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:13:33
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:13:33
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:13:43
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:13:43
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:13:53
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:13:53
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
04/25/2007 20:14:03
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'BROKERMANAGER' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 289 --------------------------------------------------------
04/25/2007 20:14:03
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------

mrgate

Posted: Wed Apr 25, 2007 6:31 am Post subject: Re: broker domain not created in the toolkit

Centurion

Joined: 28 Feb 2007
Posts: 141
Location: India

marcin.kasinski wrote:

I'm talking about queue manager logs.

You can not connect to config manager queue manager.

In this logs you will find why.

fjb_saper

Posted: Wed Apr 25, 2007 12:56 pm Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY

So is the qmgr available?
Does it have the required svrconn channel.
Does it have a listener running ?

What makes your qmgr unavailable ?
2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE

Enjoy

_________________
MQ & Broker admin

mrgate

Posted: Thu Apr 26, 2007 5:16 am Post subject:

Centurion

Joined: 28 Feb 2007
Posts: 141
Location: India

Hi my problem was solved and thanks to every one who helped me in solving this problem.

Vitor

Posted: Thu Apr 26, 2007 6:01 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

rock wrote:

Hi my problem was solved and thanks to every one who helped me in solving this problem.

Please post the solution for the benefit of future searchers.

And well done you!

_________________
Honesty is the best policy.
Insanity is the best defence.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » broker domain not created in the toolkit

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