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 » Creating Default Configuration Manager

Post new topic  Reply to topic
 Creating Default Configuration Manager « View previous topic :: View next topic » 
Author Message
Gemz
PostPosted: Tue Sep 02, 2008 1:35 am    Post subject: Creating Default Configuration Manager Reply with quote

Centurion

Joined: 14 Jan 2008
Posts: 124
Hi,

I tried to create a default configuration manager and am getting the following error in the log file while creating the database.

!SESSION 2008-09-02 10:14:54.466 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223ifx-20070323 (JIT enabled)
J9VM - 20070322_12058_lHdSMR
JIT - 20070109_1805ifx3_r8
GC - WASIFIX_2007
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product com.ibm.etools.msgbroker.tooling.ide
Command-line arguments: -os win32 -ws win32 -arch x86 -product com.ibm.etools.msgbroker.tooling.ide

!ENTRY org.eclipse.help 4 0 2008-09-02 10:15:08.935
!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 org.apache.xerces.jaxp.SAXParserImpl.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.internal.help.WorkbenchHelpSystem.displayHelpResource(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.url.ShowHelpURLHandler.showHelpTopic(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.showHelpTopic(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.doExecute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.internal.intro.impl.model.url.IntroURL.execute(Unknown Source)
at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartLocationListener.changing(Unknown Source)
at org.eclipse.swt.browser.Browser$2.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.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
at org.eclipse.core.launcher.Main.run(Unknown Source)
at org.eclipse.core.launcher.Main.main(Unknown Source)


can you light on wer the prob is...?
Back to top
View user's profile Send private message
jeeth_m
PostPosted: Tue Sep 02, 2008 2:38 am    Post subject: Reply with quote

Voyager

Joined: 21 Jan 2002
Posts: 93
Gemz,
Could you try creating the config manager by yourself. I mean without using the toolkit.

Jeeth
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
Gemz
PostPosted: Tue Sep 02, 2008 3:03 am    Post subject: Reply with quote

Centurion

Joined: 14 Jan 2008
Posts: 124
I got the above exception while creating the database using default configuration wizard.

Wen i tried to create the db in command prompt, i got the following result.

C:\Program Files\IBM\MQSI\6.1>mqsicreatedb DEFBKDB1 -i mbuser -a passwd1
BIP9824I: Creating the DatabaseInstanceMgr Service Component.
BIP9832I: Starting the DatabaseInstanceMgr Service Component.
BIP9833I: Stopping the DatabaseInstanceMgr Service Component.
BIP9826I: Removing the DatabaseInstanceMgr Service Component.
BIP8024E: Unable to locate the component's executable.
The component's executable is not in the expected directory.
Ensure that the product has not been moved from its installation directory. Check that executable 'bipservice' is in the product's 'bin' directory.

I checked the bipservice file.
bipservice2.exe file is present in 'C:\Program Files\IBM\MQSI\6.1\bin' folder.

I think bipservice2.exe is the file that expects.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Tue Sep 02, 2008 8:34 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
You should have a bipservice.exe file inside your bin directory. I don't know where bipservice2.exe comes from; check your install was successful and that it hasn't been tampered with.
Back to top
View user's profile Send private message
Gemz
PostPosted: Tue Sep 02, 2008 9:08 am    Post subject: Reply with quote

Centurion

Joined: 14 Jan 2008
Posts: 124
Even i am not sure how bipservice2 has come.

If I rename the bipservice2.exe to bipservice.exe, I am able to create all the default configuration components.

But wen i try to deploy the bar file, am getting the following error in Event log.
-----------------
BIP4395E: Java exception: 'com.ibm.broker.schemadeploy.MbXSDInternalError'; thrown from class name: 'com.ibm.broker.schemadeploy.MbXSDDeployDirector', method name: 'compileMessageSetSchemas', file: 'MbXSDDeployDirector.java', line: '525'

The message contains that data associated with a Java exception.

No user action required.
-----------------
BIP5024E: The creation and preprocessing of the XML schemas in message set 'AVL_IAR_INS_UP_DEL.xsdzip' has failed.

Review previous messages to find out why the error occurred.
----------------

Now do i need to reinstall the broker and toolkit...? !!!!
Back to top
View user's profile Send private message
mqmatt
PostPosted: Tue Sep 02, 2008 9:22 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
Kimbert may be able to pinpoint the parser error for you.
If not, you may have to reinstall the runtime; I'm concerned how your runtime install got messed up, forcing you to rename executable files. The errors are not toolkit ones, so you shouldn't need to reinstall this.
Back to top
View user's profile Send private message
kimbert
PostPosted: Tue Sep 02, 2008 2:57 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
The error message from the XMLNSC parser is an internal error. First thing to do is re-install the runtime and see whether it goes away. If not, post again on this thread and we can take it from there.
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 » Creating Default Configuration Manager
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.