Author |
Message
|
pfarrel |
Posted: Fri Jul 10, 2009 3:54 am Post subject: MQ Explorer plugin IS02 error |
|
|
Centurion
Joined: 16 Mar 2004 Posts: 120 Location: Kansas City
|
Hello, I'm not sure if this is an MQ question or a Broker question.
I installed the IS02 Support Pack plugin to the MQ explorer. It seems to be working for the most part so far, but I keep getting an error from time to time.
I have added a couple of Config Managers to the display, and I can browse the Execution Groups, and the flows. However, sometimes when I click on a flow name in the left pane, I get a box popping up which says
An error has ocurred. See error log for more details.
Can someone please tell me where this error log is ?
I have searched my computer ( which runs Windows/XP ) for a file that was updated at the time the error ocurred, no luck there. I have looked on the server where the config manager resides, no luck there either.
Thanks. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Jul 10, 2009 4:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
This is an Eclipse error.
It's gonna be in the .log file in your workspace .metadata directory. |
|
Back to top |
|
 |
pfarrel |
Posted: Fri Jul 10, 2009 5:14 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004 Posts: 120 Location: Kansas City
|
The plugin appears to have created a new workspace at the following location:
C:\Documents and Settings\<userid>\Application Data\IBM\MQ Explorer\.metadata
This is not the location of my workspace that I use from the Broker Toolkit.
In the new workspace, there is a file called .log. ( strange that the name begins with a period ).
In this .log file, there are lots of errors, here are a few:
!MESSAGE Error occurred processing file toc.xml.
!MESSAGE Error loading Table of Contents file /com.ibm.mq.csqsao.doc/toc.xml.
!MESSAGE Failed to parse Table of Contents file, URL: file:///com.ibm.mq.csqsao.doc/toc.xml at line: 143, column: 3.
The element type "topic" must be terminated by the matching end-tag "</topic>".
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.runtime".
!STACK 0
java.lang.NullPointerException
at com.ibm.etools.wmadmin.broker.explorer.FlowTreeNode.FlowContentPage.getAllProperties
I'm not sure what this all means. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Jul 10, 2009 5:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It's not the plugin that created that workspace. It's MQ Explorer. That's the default workspace location for MQ Explorer.
If you change MQ Explorer to run in an Eclipse workbench (I think IS02 still asks you to do that?), then you can change workspaces manually or ask it to ask you every time it starts up.
You can ignore the errors about the table of contents. You might want to just update MQ to get any MQ Explorer fixes, though.
Other errors mean other things... this .log file is basically the stderr for the Eclipse environment that both IS02 and MQ Explorer runs in.
Look for IS02 specific errors, and see if there's something meaningful. There may not be.
It may help to run strmqcfg -i and then strmqcfg -c as well. |
|
Back to top |
|
 |
pfarrel |
Posted: Fri Jul 10, 2009 6:20 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004 Posts: 120 Location: Kansas City
|
OK, I See how to change the workbench location, thanks.
I tried selecting a message flow, got the error box, and then looked at the .log file to see what new messages there were. One new message.
!ENTRY org.eclipse.core.runtime 4 2 Jul 10, 2009 09:15:51.200
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.runtime".
!STACK 0
java.lang.NullPointerException
at com.ibm.etools.wmadmin.broker.explorer.FlowTreeNode.FlowContentPage.getAllProperties(FlowContentPage.java:236)
at com.ibm.etools.wmadmin.broker.explorer.FlowTreeNode.FlowContentPage.setObject(FlowContentPage.java:100)
at com.ibm.mq.explorer.ui.internal.views.MQContentView.showContentPage(MQContentView.java:413)
at com.ibm.mq.explorer.ui.internal.views.MQContentView.showSelection(MQContentView.java:488)
at com.ibm.mq.explorer.ui.internal.views.MQContentView.selectionChanged(MQContentView.java:456)
and a lot more lines that begin with at.
I assume this is how java reports problems. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Jul 10, 2009 6:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
pfarrel wrote: |
and a lot more lines that begin with at.
I assume this is how java reports problems. |
This how Eclipse formats the way Java reports problems.
It seems that some Flow in your environment is reporting a NULL value for a property and the IS02 code is not handling this as gracefully as it could. This is maybe a bug with IS02. You may be able to avoid it if you manually refresh the MQ Navigator tree view, by clicking the little arrows-in-a-circle-button.
Or, again, there may be some inconsistencies with the cached plugin configurations, that should be resolved with strmqcfg -i/strmcfg -c. |
|
Back to top |
|
 |
PhilBlake |
Posted: Tue Jul 14, 2009 12:15 am Post subject: |
|
|
 Acolyte
Joined: 25 Oct 2005 Posts: 64
|
Quote: |
It seems that some Flow in your environment is reporting a NULL value for a property and the IS02 code is not handling this as gracefully as it could. This is maybe a bug with IS02. |
Which version of IS02 are you using ? Make sure you are using the latest version for WMQ v7 (I'm told this fixes the NPE problems). If this is still a problem, then append here and I will speak with the author of the plug-in.
Phil |
|
Back to top |
|
 |
zpat |
Posted: Tue Jul 14, 2009 1:40 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I've had a lot of similar problems with IS02 on MQ v6 and had to remove it in the end to get MQ explorer working again.
I don't have MQ v7.
Given that IS02 seems to be the preferred IBM direction for operating the broker - these experiences (esp on MQ v6) are not that great. |
|
Back to top |
|
 |
PhilBlake |
Posted: Tue Jul 14, 2009 3:17 am Post subject: |
|
|
 Acolyte
Joined: 25 Oct 2005 Posts: 64
|
|
Back to top |
|
 |
zpat |
Posted: Tue Jul 14, 2009 3:34 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Can this new explorer support pac be installed alongside a MQ v6 QM?
Will it affect my broker toolkit at all?
Last edited by zpat on Tue Jul 14, 2009 3:57 am; edited 1 time in total |
|
Back to top |
|
 |
ramires |
Posted: Tue Jul 14, 2009 3:38 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
I also had a lot problems with IS02, never managed to fix them, basically it's behavior is not consistent, and also slower than the standard toolkit provided with message broker
Regards |
|
Back to top |
|
 |
zpat |
Posted: Tue Jul 14, 2009 3:56 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I complained about the quality of IS02 at Hursley the other day and was reminded that it is a supported product - so you can raise defects against it with a PMR (should you have the time to spare!). |
|
Back to top |
|
 |
PhilBlake |
Posted: Tue Jul 14, 2009 4:59 am Post subject: |
|
|
 Acolyte
Joined: 25 Oct 2005 Posts: 64
|
zpat wrote: |
Can this new explorer support pac be installed alongside a MQ v6 QM? |
MS0T is designed to run standalone (without WMQ installed). A quote from the MS0T download page
Quote: |
You can install this SupportPac alongside an existing MQ Client installation. You can also install this SupportPac alongside an existing MQ V7.0 server installation provided that both are at the same version level. |
zpat wrote: |
Will it affect my broker toolkit at all? |
MS0T uses its own version of Eclipse, so there is no shell sharing with other products. This can be seen as a good and as a bad thing !
Phil |
|
Back to top |
|
 |
zpat |
Posted: Tue Jul 14, 2009 5:06 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
My suspicious mind reads this
Quote: |
You can also install this SupportPac alongside an existing MQ V7.0 server installation provided that both are at the same version level |
as meaning that you can't install it alongside a MQ server installation at a different level (like MQ v6).
I can't afford to mess up my PC unfortunately. |
|
Back to top |
|
 |
|