Author |
Message
|
jjordan |
Posted: Thu Jan 30, 2014 7:00 am Post subject: Websphere MQ (IBM Integration) Explorer Blank Screen |
|
|
Novice
Joined: 14 Oct 2005 Posts: 17 Location: Portland, ME
|
MQ Client Version: 7.5.0.2
Integration Bus Version: 9.0.0.1
Running on Windows V7 Enterprise SP1 - 32 bit
The app worked perfectly last week, and now it suddenly has stopped working.
In the MQ (Integration) Explorer, I'm getting a blank window (after a long start up period) when I launch the app from the installed menu option (it runs strmqcfg.cm -d -c). I have not options under Window ... Show View.
Details of the error are at the end of the post.
Any thoughts as to the cause and resolution would be greatly appreciated.
Thanks,
Jeff
ERROR LOG DETAILS:
Looking at the Help ... About ... Installation Details ... View Error log, I see:
!SESSION 2014-01-30 08:32:50.960 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr13fp2-20130423_146146 (JIT enabled, AOT enabled)
J9VM - 20130423_146146
JIT - r9_20130108_31100ifx1
GC - 20121212_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean
!ENTRY org.eclipse.osgi 0 0 2014-01-30 08:32:58.476
!MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: C:\Program Files\IBM\WebSphere MQ\MQExplorer\eclipse\configuration\org.eclipse.osgi
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.mft.config.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.datapower.model.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.datapower.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.explorer.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.explorer.trace.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.model.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.policysets.model.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.policysets.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.policysets.provider.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.runtime.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.security.model.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.security.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "com.ibm.etools.wmadmin.broker.stats.nl1" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "org.aspectj.runtime" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "org.eclipse.birt" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "org.eclipse.emf" are ignored. The bundle is not marked as singleton.
!ENTRY org.eclipse.equinox.registry 2 0 2014-01-30 08:33:42.851
!MESSAGE The extensions and extension-points from the bundle "org.eclipse.emf.edit.ui" are ignored. The bundle is not marked as singleton. |
|
Back to top |
|
 |
zpat |
Posted: Thu Jan 30, 2014 8:29 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I have found MBX and IIBX explorer to be quite buggy, with problems installing them, null pointer exceptions and screen corruptions.
However a very helpful AVP rep gave me this advice, both when installing MBX/IIBX and when running it. Make sure the following environment variables are not set.
JAVA_TOOL_OPTIONS
JAVA_OPTIONS
IBM_JAVA_OPTIONS
This has helped - but not entirely eliminated the buggy and slow nature of MQ explorer and/or MBX/IIBX (even on the latest hardware) for me. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Jan 30, 2014 8:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It sounds like it's a permissions issue with the file system.
I suspect zpat is running into similar kinds of things, since I've never found the same issues - but I only ever run it on a laptop where I have full admin rights. |
|
Back to top |
|
 |
zpat |
Posted: Thu Jan 30, 2014 8:54 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I've tried installing them as admin and so on - although IBM need to understand that in the real world - people don't generally have full admin rights on their corporate PCs.
The Java options advice has been the best so far and I finally got IIBX 9001 to install. Now I can use it for about 10 mins until something breaks (probably memory issues in the JVM). _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Jan 30, 2014 8:57 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
@jjordan
Jeff, have you tried running it (IIBExplorer) with elevated privilege (contact admin)?
Do you run into the same problems running it that way?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jjordan |
Posted: Thu Jan 30, 2014 1:38 pm Post subject: |
|
|
Novice
Joined: 14 Oct 2005 Posts: 17 Location: Portland, ME
|
I went ahead and ran it as "administrator", with the same result. It's a good thought, though...
Interestingly, the error log DID NOT include the
!ENTRY org.eclipse.osgi 0 0 2014-01-30 08:32:58.476
!MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: C:\Program Files\IBM\WebSphere MQ\MQExplorer\eclipse\configuration\org.eclipse.osgi
entry this time (or the subsequent attempts I made, either...)
It was just that first time I tried this morning... |
|
Back to top |
|
 |
jjordan |
Posted: Mon Feb 03, 2014 6:26 am Post subject: |
|
|
Novice
Joined: 14 Oct 2005 Posts: 17 Location: Portland, ME
|
**RESOLVED**
I deleted the .metadata folder in the workspace, and restarted the explorer (leaving the other folders there intact). When I restarted, it came up (taking some time to rebuild the .metadata folder, I presumed), with my queue managers and integration bus servers showing up.
Thanks to all for your input and discussion!
Jeff |
|
Back to top |
|
 |
|