| Author |
Message
|
| kotla.satya |
 Posted: Tue Apr 15, 2008 1:38 pm Post subject: MQ Explorer error opening Navigator or content panel |
 |
|
Apprentice
Joined: 30 Jan 2006
Posts: 40
Location: chennai-India
|
WMQ 6.0.2.1 is installed on Windows XP.
I am able to create qmgr in command prompt and able to see it.
When I open the MQ explorer the below error is displayed and try to see navigator (window -> show view ->Websphere MQ explorer -Navigator),it shows below error.
Unable to create part : Websphere MQ Explorer -Navigator
I see error in log file as
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 2308.
Could you pl. let me know where might be the problem. |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Tue Apr 15, 2008 8:24 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
which process has pid as 2308.???
is it javaw.exe ??
_________________
Cheers |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Tue Apr 15, 2008 8:34 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear Satya,
Did u check the event viewer log in windows? There u ell get more explanation 
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Apr 15, 2008 11:07 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
click on reset perspective and see if navigator appears...
_________________
Cheers |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 16, 2008 3:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also, try strmqcfg -c.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kotla.satya |
| Posted: Wed Apr 16, 2008 5:24 am Post subject: |
|
|
Apprentice
Joined: 30 Jan 2006
Posts: 40
Location: chennai-India
|
The process id is of javaw.exe.
I have tried the reset perspective option and strmqcfg -c option. I see the same error,the content pane and navigator pane are not opening.
How to see the windows event viewer log?.
Thanks & Regards
Satya |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 16, 2008 5:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Click start, select Run..., type eventvwr, click OK
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| kotla.satya |
| Posted: Wed Apr 16, 2008 5:43 am Post subject: |
|
|
Apprentice
Joined: 30 Jan 2006
Posts: 40
Location: chennai-India
|
The event viewer points to error log files.
It says the process is javaw.exe
is it possible to reinstall the MQ explorer alone. |
|
| Back to top |
|
|
| manicminer |
| Posted: Wed Apr 16, 2008 7:01 am Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
If the explorer fails, it might have written an FDC file to the errors directory. Are there and FDC's and does one of them from the Explorer have a full java strack trace? that will give more of a hint as to the problem.
The Explorer installable standalone, so I imagine it should be possible to remove the explorer component and then re-install |
|
| Back to top |
|
|
| kotla.satya |
| Posted: Wed Apr 16, 2008 12:04 pm Post subject: |
|
|
Apprentice
Joined: 30 Jan 2006
Posts: 40
Location: chennai-India
|
| manicminer wrote: |
If the explorer fails, it might have written an FDC file to the errors directory. Are there and FDC's and does one of them from the Explorer have a full java strack trace? that will give more of a hint as to the problem.
The Explorer installable standalone, so I imagine it should be possible to remove the explorer component and then re-install |
You are correct. I have mentioned the errors from the fdc files. It basically points to javaw.exe.
Is the explorer program 'IBM Websphere Eclipse Platform'?. |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Apr 16, 2008 12:04 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| manicminer wrote: |
| If the explorer fails, it might have written an FDC file to the errors directory. Are there and FDC's and does one of them from the Explorer have a full java strack trace? |
MQSeries throws FDCs, not Eclipse (Explorer).
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 16, 2008 12:11 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| EddieA wrote: |
| manicminer wrote: |
| If the explorer fails, it might have written an FDC file to the errors directory. Are there and FDC's and does one of them from the Explorer have a full java strack trace? |
MQSeries throws FDCs, not Eclipse (Explorer). |
I'm going to have to disagree with you...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| manicminer |
| Posted: Thu Apr 17, 2008 1:15 am Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
| jefflowrey wrote: |
| EddieA wrote: |
| manicminer wrote: |
| If the explorer fails, it might have written an FDC file to the errors directory. Are there and FDC's and does one of them from the Explorer have a full java strack trace? |
MQSeries throws FDCs, not Eclipse (Explorer). |
I'm going to have to disagree with you... |
Me too! The MQ Explorer is one of many programs that make up WebSphere MQ and as such has an FDC mechanism, any failure on a server install will result in an appropriate FDC being written, this in turn will contain a java stack trace of what went wrong. These FDC's are written my MQ in exactly the same way as an FDC from any other failing WebSphere MQ process.
These FDC's can also be used during plug-in development as plug-in errors in some circumstances result in an FDC being written telling you what went wrong.
For example (from the V7 beta), below is a failure from the MQ Explorer, note SCCS info says eclipse/common/amqjxtra.c
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu April 03 2008 09:19:20 BST |
| UTC Time :- 1207210760.152519 |
| UTC Time Offset :- 0 (GMT) |
| Host Name :- ukfadsrowles01.infor.com |
| Operating System :- Linux 2.6.24.3-50.fc8 |
| PIDS :- 5724H7224 |
| LVLS :- 7.0.0.0 |
| Product Long Name :- WebSphere MQ for Linux (x86 platform) |
| Vendor :- IBM |
| Probe Id :- UNU56010 |
| Application Name :- MQM |
| Component :- RunMQApplication.run |
| SCCS Info :- eclipse/common/amqjxtra.c, 1.21 |
| Line Number :- 610 |
| Build Date :- Mar 20 2008 |
| CMVC level :- p000-S080320 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000500 (srowles) |
| Program Name :- javaw |
| Addressing mode :- 32-bit |
| Process :- 28272 |
| Process(Thread) :- 28272 |
| Thread :- 2 |
| ThreadingModel :- PosixThreads |
| QueueManager :- test1 |
| Last HQC :- 1.0.0-962176 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- Unknown(C37C) |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- |
| |
+-----------------------------------------------------------------------------+
|
And scrolling down in the FDC there is a "Component Dumps" section that contains the stack trace:
| Code: |
Component Dumps (Thread 00000002)
------< JC "Java CommonServices" >-----
Key 1: (null) = (null)
Key 2: (null) = (null)
Key 3: (null) = (null)
com.ibm.mq.commonservices.internal.trace.Trace.getJavaStack(Trace.java:2190)
com.ibm.mq.commonservices.internal.trace.Trace.wmq_FFST(Native Method)
com.ibm.mq.commonservices.internal.trace.Trace.FFST(Trace.java:1631)
com.ibm.mq.commonservices.internal.trace.Trace.FFST(Trace.java:1867)
com.ibm.mq.commonservices.internal.trace.Trace.FFST(Trace.java:1766)
com.ibm.mq.explorer.ui.rcp.internal.base.RunMQApplication.run(RunMQApplication.java:79)
org.eclipse.ui.internal.intro.impl.model.url.IntroURL.runAction(IntroURL.java:282)
org.eclipse.ui.internal.intro.impl.model.url.IntroURL.doExecute(IntroURL.java:193)
org.eclipse.ui.internal.intro.impl.model.url.IntroURL$1.run(IntroURL.java:144)
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
org.eclipse.ui.internal.intro.impl.model.url.IntroURL.execute(IntroURL.java:141)
org.eclipse.ui.internal.intro.impl.swt.PageWidgetFactory$1.linkActivated(PageWidgetFactory.java:63)
org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:228)
org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:316)
org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:300)
org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:119)
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
com.ibm.mq.explorer.ui.rcp.internal.base.RcpApplication.run(RcpApplication.java:145)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:615)
org.eclipse.equinox.internal.app.EclipseAppContainer.callMethod(EclipseAppContainer.java:572)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:171)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
|
Just because I have a low post count, doesn't mean I don't know what I'm talking about   |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Apr 17, 2008 8:50 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| manicminer wrote: |
| Just because I have a low post count, doesn't mean I don't know what I'm talking about |
I never look at the post count, just the question/comment posted.
I'm very happy to be corrected here.  Trying to work out what happened when the Explorer "fails" has always been a pain.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
