Topic
  • 10 replies
  • Latest Post - ‏2014-08-28T13:03:17Z by luis_munoz
SystemAdmin
SystemAdmin
642 Posts

Pinned topic ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

‏2012-07-10T09:46:17Z |
Hi, I tried the Garbage Collection and Memory Visualizer (GCMV) Report
and get the following error.

com.ibm.java.diagnostics.visualizer
....
....
JAVA_HOME=/application/isa5beta/ISA5/_jvm/jre
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr10-20111208_01(SR10))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr10-20111207_96808 (JIT enabled, AOT enabled)
J9VM - 20111207_096808
JIT - r9_20111107_21307ifx1
GC - 20110519_AA)
JCL - 20111104_02

Command exited with non-zero status 13
real 6.79
user 8.05
sys 0.36

rc=13
Where can I find a description of rc=13
Thank you for any help
Best regards
Klaus Pretsch
Updated on 2012-07-11T17:32:40Z at 2012-07-11T17:32:40Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    642 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2012-07-10T12:38:46Z  
    I enabled X11 in my Putty Session (Tunnel) and now I get.
    PuTTY X11 proxy: wrong authentication protocol attemptedCommand exited with non-zero status 13
    real 6.70
    user 7.73
    sys 0.28

    rc=13

    Also I get
    !ENTRY org.eclipse.osgi 4 0 2012-07-10 13:58:08.067
    !MESSAGE Application error
    !STACK 1
    org.eclipse.swt.SWTError: No more handles gtk_init_check() failed
    at org.eclipse.swt.SWT.error(SWT.java:4109)

    I tried xclock befor I started ISA and it works fine.
    If ISA is started xclock fail (hanging putty session)

    My OS is SUSE Linux Enterprise Server 11 SP1 (x86_64)

    Thank you for any hint.
    Best regards
    Klaus
  • SystemAdmin
    SystemAdmin
    642 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2012-07-10T17:18:54Z  
    I enabled X11 in my Putty Session (Tunnel) and now I get.
    PuTTY X11 proxy: wrong authentication protocol attemptedCommand exited with non-zero status 13
    real 6.70
    user 7.73
    sys 0.28

    rc=13

    Also I get
    !ENTRY org.eclipse.osgi 4 0 2012-07-10 13:58:08.067
    !MESSAGE Application error
    !STACK 1
    org.eclipse.swt.SWTError: No more handles gtk_init_check() failed
    at org.eclipse.swt.SWT.error(SWT.java:4109)

    I tried xclock befor I started ISA and it works fine.
    If ISA is started xclock fail (hanging putty session)

    My OS is SUSE Linux Enterprise Server 11 SP1 (x86_64)

    Thank you for any hint.
    Best regards
    Klaus
    Java RC 13 is a generic java error. Usually because of a classpath problem or in my case I was getting RC 13 because it didn't like the gcmv heapsize settings.

    From looking at your JAVA home below, I'm assuming you are using the standalone client and not the ear?

    With that assumption, I see that you installed into a non-standard directory.

    Under the release notes on line 74, it says:
    ##Installing

    ###Team Server or Desktop application
    Extract the IBM Support Assistant zip or tar.gz package to a location on your
    file system. This will create an 'ISA5' subdirectory and you will then be ready
    to start the application server.
    (eg. C:\IBM or /opt/ibm)

    So, I would try installing into that directory first. You may also find line 52 helpful regarding XDisplay on linux.

    ###X11 DISPLAY
    On Linux, ISA makes use of X11 to generate images included in problem
    determination analysis output. If the DISPLAY
    environment variable is not valid, then some analysis output may indicate:

    Xlib: connection to ":0.0" refused by server

    **TIP** In a 'headless' configuration, an X11 virtual frame buffer can be used.
    The relevant Red Hat RPM is:

    xorg-x11-server-Xvfb-1.1.1-48.76.el5_6.4

    With this RPM installed,a virtual frame buffer accessible by way of "DISPLAY=:1"
    can be set up with the command:

    /usr/bin/Xvfb :1 -screen 0 1024x768x16 &

    If DISPLAY is not set, ISA will try "DISPLAY=:1" as a default.

    Furthermore, if there is a firewall involved, you may not get to port 10912 (default port for gcmv).

    Finally, if you really want to keep your installation directory, the code was written with the idea that you can modify in any way you like. The GCMV is a separate application, with separate javahome parameters. You might be able to modify start_mat.sh under Toolbox/bin to your ISA5 install directory to include the proper javahome parameters.

    Either way, I found the readme's, release notes, and documentation to be extremely helpful. I would start there.
  • SystemAdmin
    SystemAdmin
    642 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2012-07-11T13:27:17Z  
    I tried several suggestions without success. I talked to our Linux Team and they told me that they only install a minimum of the Linux Systems RPM. No they asked me for a list of linux RPM resources used by ISA5.
    Also I like to know if SUSE LINUX is supported!
    regards Klaus
  • SystemAdmin
    SystemAdmin
    642 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2012-07-11T17:32:40Z  
    I tried several suggestions without success. I talked to our Linux Team and they told me that they only install a minimum of the Linux Systems RPM. No they asked me for a list of linux RPM resources used by ISA5.
    Also I like to know if SUSE LINUX is supported!
    regards Klaus
    If you don't have direct administrative access to the server, it's going to be a bit difficult to install. I tried it on my desktop first. Got a good proof of concept going, then gathered requirements to present to my administrative team to have them install this product.
  • BaltoSteve
    BaltoSteve
    30 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2013-10-07T21:26:25Z  

    I just installed ISA v5 b3 on a 64-bit Windows server, and I'm getting a similar cc13 from GCMV.  The error is in the attached doc -

     

    Attachments

  • BaltoSteve
    BaltoSteve
    30 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2013-10-08T17:52:27Z  

    Also Memory Analyzer doesn't work out of the box, another missing file -

    Cannot find

    /IBM/ISAv5b3/ISA5/ToolBox/ISAToolsAntTasks/isatoolsanttasks.xml imported from C:\IBM\ISAv5b3\ISA5\ToolBox

    \com.ibm.java.diagnostics.memory.analyzer\runmat.xml

  • po.bbh
    po.bbh
    4 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2013-11-08T13:24:06Z  

    Same problem here, when trying to launch "report" version on GCMV. I was actually following tutorial "[0000] Example Case" on ISA 5 beta3

    Why a headless version of GCMV needs to use SWT?

    !SESSION 2013-11-08 08:07:38.157 -----------------------------------------------
    eclipse.buildId=M20110210-1200
    java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr11-20120801_118201 (JIT enabled, AOT enabled)
    J9VM - 20120801_118201
    JIT  - r9_20120608_24176ifx1
    GC   - 20120516_AA
    BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
    Framework arguments:  -application com.ibm.java.diagnostics.visualizer.headless.application -f /home/(removed)/ISA5/isa/cases/0000/native_stderr.log -o /home/(removed)/ISA5/isa/cases/0000/native_stderr.log-visualizer_ISA_PD/Performance -p Performance
    Command-line arguments:  -consoleLog -application com.ibm.java.diagnostics.visualizer.headless.application -f /home/(removed)/ISA5/isa/cases/0000/native_stderr.log -o /home/(removed)/ISA5/isa/cases/0000/native_stderr.log-visualizer_ISA_PD/Performance -p Performance
    !ENTRY org.eclipse.osgi 4 0 2013-11-08 08:07:44.796
    !MESSAGE Application error
    !STACK 1
    org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
        at org.eclipse.swt.SWT.error(SWT.java:4109)
        at org.eclipse.swt.widgets.Display.createDisplay(Display.java:902)
        at org.eclipse.swt.widgets.Display.create(Display.java:890)
        at org.eclipse.swt.graphics.Device.<init>(Device.java:154)
        at org.eclipse.swt.widgets.Display.<init>(Display.java:499)
        at org.eclipse.swt.widgets.Display.<init>(Display.java:490)
        at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:708)
        at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
        at com.ibm.java.diagnostics.visualizer.headless.Application.start(Application.java:47)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
    An error has occurred. See the log file
    /tmp/com.ibm.java.diagnostics.visualizer-t1108.080737.693337.d/eclipse/workspace/.metadata/.log.

     

    Updated on 2013-11-08T13:28:42Z at 2013-11-08T13:28:42Z by po.bbh
  • rbwright
    rbwright
    227 Posts

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2013-11-11T22:07:17Z  
    • po.bbh
    • ‏2013-11-08T13:24:06Z

    Same problem here, when trying to launch "report" version on GCMV. I was actually following tutorial "[0000] Example Case" on ISA 5 beta3

    Why a headless version of GCMV needs to use SWT?

    !SESSION 2013-11-08 08:07:38.157 -----------------------------------------------
    eclipse.buildId=M20110210-1200
    java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr11-20120801_118201 (JIT enabled, AOT enabled)
    J9VM - 20120801_118201
    JIT  - r9_20120608_24176ifx1
    GC   - 20120516_AA
    BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
    Framework arguments:  -application com.ibm.java.diagnostics.visualizer.headless.application -f /home/(removed)/ISA5/isa/cases/0000/native_stderr.log -o /home/(removed)/ISA5/isa/cases/0000/native_stderr.log-visualizer_ISA_PD/Performance -p Performance
    Command-line arguments:  -consoleLog -application com.ibm.java.diagnostics.visualizer.headless.application -f /home/(removed)/ISA5/isa/cases/0000/native_stderr.log -o /home/(removed)/ISA5/isa/cases/0000/native_stderr.log-visualizer_ISA_PD/Performance -p Performance
    !ENTRY org.eclipse.osgi 4 0 2013-11-08 08:07:44.796
    !MESSAGE Application error
    !STACK 1
    org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
        at org.eclipse.swt.SWT.error(SWT.java:4109)
        at org.eclipse.swt.widgets.Display.createDisplay(Display.java:902)
        at org.eclipse.swt.widgets.Display.create(Display.java:890)
        at org.eclipse.swt.graphics.Device.<init>(Device.java:154)
        at org.eclipse.swt.widgets.Display.<init>(Display.java:499)
        at org.eclipse.swt.widgets.Display.<init>(Display.java:490)
        at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:708)
        at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
        at com.ibm.java.diagnostics.visualizer.headless.Application.start(Application.java:47)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
    An error has occurred. See the log file
    /tmp/com.ibm.java.diagnostics.visualizer-t1108.080737.693337.d/eclipse/workspace/.metadata/.log.

     

    Hi Piotr,

    The report edition of GCMV generates graphical reports and it takes advantage of the same code to do that as the GUI version of the tool. This is why you see SWT in the stack trace.

    I believe the problem you reported occurred because GCMV, and other tools such at PMAT, need an X11 display process to produce those graphical reports. The ISA 5 Beta 3 release notes suggest using an X11 virtual frame buffer to do that and then to set the DISPLAY environment variable in the shell running ISA to that display value. Here's a link to the release notes: http://www.ibm.com/support/docview.wss?uid=swg27036238 . Here's the text from the relevant section:

    ###X11 DISPLAY
    On Linux, IBM Support Assistant makes use of X11 to generate images included
    in problem determination analysis output. If the DISPLAY environment
    variable is not valid, then some analysis output may indicate:

    Xlib: connection to ":0.0" refused by server

    **TIP** In a ' headless' configuration, an X11 virtual frame buffer can be
    used. The relevant Red Hat RPM is:

    xorg-x11-server- Xvfb-1.1.1-48.76.el5_6.4

    With this RPM installed,a virtual frame buffer accessible by way of
    "DISPLAY=:1" can be set up with the command:

    /usr/bin/Xvfb :1 -screen 0 1024x768x16 &

    If DISPLAY is not set, ISA will try "DISPLAY=:1" as a default.
     

    Regards,

    Russell

  • byronical
    byronical
    1 Post

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2014-02-05T02:50:07Z  
    • rbwright
    • ‏2013-11-11T22:07:17Z

    Hi Piotr,

    The report edition of GCMV generates graphical reports and it takes advantage of the same code to do that as the GUI version of the tool. This is why you see SWT in the stack trace.

    I believe the problem you reported occurred because GCMV, and other tools such at PMAT, need an X11 display process to produce those graphical reports. The ISA 5 Beta 3 release notes suggest using an X11 virtual frame buffer to do that and then to set the DISPLAY environment variable in the shell running ISA to that display value. Here's a link to the release notes: http://www.ibm.com/support/docview.wss?uid=swg27036238 . Here's the text from the relevant section:

    ###X11 DISPLAY
    On Linux, IBM Support Assistant makes use of X11 to generate images included
    in problem determination analysis output. If the DISPLAY environment
    variable is not valid, then some analysis output may indicate:

    Xlib: connection to ":0.0" refused by server

    **TIP** In a ' headless' configuration, an X11 virtual frame buffer can be
    used. The relevant Red Hat RPM is:

    xorg-x11-server- Xvfb-1.1.1-48.76.el5_6.4

    With this RPM installed,a virtual frame buffer accessible by way of
    "DISPLAY=:1" can be set up with the command:

    /usr/bin/Xvfb :1 -screen 0 1024x768x16 &

    If DISPLAY is not set, ISA will try "DISPLAY=:1" as a default.
     

    Regards,

    Russell

    I had the same problem - exce[t I run ISA under root and a sudo xhost + resolved the problem

    bc3801@wjvq040:~]$ sudo xhost +
    access control disabled, clients can connect from any host
    bc3801@wjvq040:~]$

  • luis_munoz
    luis_munoz
    1 Post

    Re: ISA 5 Garbage Collection and Memory Visualizer (GCMV) [Report]

    ‏2014-08-28T13:03:17Z  
    • byronical
    • ‏2014-02-05T02:50:07Z

    I had the same problem - exce[t I run ISA under root and a sudo xhost + resolved the problem

    bc3801@wjvq040:~]$ sudo xhost +
    access control disabled, clients can connect from any host
    bc3801@wjvq040:~]$

    the xhost + fix worked for me too