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 » Defaul Configuration wizard not working

Post new topic  Reply to topic
 Defaul Configuration wizard not working « View previous topic :: View next topic » 
Author Message
jballa
PostPosted: Fri Jun 29, 2007 4:43 am    Post subject: Defaul Configuration wizard not working Reply with quote

Newbie

Joined: 01 Mar 2007
Posts: 5

Hello,
I am working on mb6.0 on windows platform where the default configuration wizard is not working. During this wizard it is giving error as:


Task: Creating the default broker. [WBRK6_DEFAULT_BROKER] failed
If you can manually fix the issues that caused this task to fail, do so and then click Yes.
If you click Yes, the wizard starts the task again.

If you click No, the wizard rolls back all completed tasks, if roll-back is possible.

To establish why the task failed, examine this wizard's log file which can be found in the workspace
directory [C:\MBWORKSPACE\WORKSPACE1\.metadata].


I have checked the log file and the data in the log file is as follows:

!SESSION Jun 29, 2007 16:44:22.757 ---------------------------------------------
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:\IBM\MessageBrokersToolkit\6.0\eclipse\plugins\com.ibm.etools.msgbroker.tooling_6.0.0\plugin_customization.ini

!ENTRY org.eclipse.help 4 0 Jun 29, 2007 16:44:22.757
!MESSAGE Error occurred processing file toc.xml.
!STACK 0
java.lang.RuntimeException: toc label==null
at org.eclipse.help.internal.toc.Toc.<init>(Toc.java:4
at org.eclipse.help.internal.toc.TocFileParser.startElement(TocFileParser.java:114)
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(TocFileParser.java:85)
at org.eclipse.help.internal.toc.TocBuilder.buildTocFile(TocBuilder.java:70)
at org.eclipse.help.internal.toc.TocFile.build(TocFile.java:112)
at org.eclipse.help.internal.toc.TocBuilder.build(TocBuilder.java:53)
at org.eclipse.help.internal.toc.TocManager.build(TocManager.java:102)
at org.eclipse.help.internal.toc.TocManager.<init>(TocManager.java:40)
at org.eclipse.help.internal.HelpPlugin.getTocManager(HelpPlugin.java:115)
at org.eclipse.help.internal.base.HelpDisplay.displayHelpResource(HelpDisplay.java:65)
at org.eclipse.help.ui.internal.DefaultHelpUI.displayHelpResource(DefaultHelpUI.java:5
at org.eclipse.ui.help.WorkbenchHelp.displayHelpResource(WorkbenchHelp.java:267)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.showHelpTopic(IntroURL.java:258)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.doExecute(IntroURL.java:127)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.access$0(IntroURL.java:106)
at org.eclipse.ui.internal.intro.impl.model.IntroURL$1.run(IntroURL.java:100)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.intro.impl.model.IntroURL.execute(IntroURL.java:97)
at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(BrowserIntroPartLocationListener.java:55)
at org.eclipse.swt.browser.Browser$3.handleEvent(Browser.java:175)
at org.eclipse.swt.ole.win32.OleEventTable.sendEvent(OleEventTable.java:55)
at org.eclipse.swt.ole.win32.OleEventSink.notifyListener(OleEventSink.java:146)
at org.eclipse.swt.ole.win32.OleEventSink.Invoke(OleEventSink.java:120)
at org.eclipse.swt.ole.win32.OleEventSink.access$1(OleEventSink.java:96)
at org.eclipse.swt.ole.win32.OleEventSink$1.method6(OleEventSink.java:70)
at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:115)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1473)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2430)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
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)
can anyone help me in solving this problem.
Back to top
View user's profile Send private message Yahoo Messenger
jbanoop
PostPosted: Fri Jun 29, 2007 6:11 am    Post subject: Reply with quote

Chevalier

Joined: 17 Sep 2005
Posts: 401
Location: SC

I would say dump the default configuration wizard and go ahead and create the things on your own from the command console.
After all , all it does is run a script and give awfully long names to the QMs.

The error seems to be an toolkit eclipse error.
Regards,
Anoop
Back to top
View user's profile Send private message Yahoo Messenger
Vitor
PostPosted: Fri Jun 29, 2007 6:29 am    Post subject: Reply with quote

Grand High Poobah

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

For what it's worth, we gave up on the wizard (only one successful use by one now very smug individual) and created the material long hand.

And no, I wasn't the guy it worked for.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Fri Jun 29, 2007 9:20 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

Do make sure you're on the latest ifix. There was an error like this a while back that was fixed.
I use the DCW all the time, but then again I'm too lazy to write my own scripts
Back to top
View user's profile Send private message
EddieA
PostPosted: Fri Jun 29, 2007 9:39 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

That's the wrong log file you're looking at. There's another one, that has, from memory, "wizard" as part of it's name. That's the one you need to look at.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
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 » Defaul Configuration wizard not working
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.