Topic
  • 2 replies
  • Latest Post - ‏2013-03-28T19:31:59Z by rogern
SystemAdmin
SystemAdmin
1086 Posts

Pinned topic Java was started but returned exit code=1073807364

‏2013-03-26T16:28:58Z |
During the past couple days, several users have started experiencing the attached error while using RDz. The symptoms are that RDz hangs with the hourglass. Upon closing the unresponsive RDz, the window shown in the attached file is present suggesting a Java error. Has anyone seen this error or have any suggestions on where to start looking for a cause.

We are running RDz version 8.5.0 and Java Version 6 Update 43 (build 1.6.0_43-b01).
Thanks,
Mike P.
SECU
Updated on 2013-03-28T19:31:59Z at 2013-03-28T19:31:59Z by rogern
  • SystemAdmin
    SystemAdmin
    1086 Posts

    Re: Java was started but returned exit code=1073807364

    ‏2013-03-28T13:16:55Z  
    We recycled RSE on ZOS and the problem resolved itself. When shutting down RSE, one of the services was hung and had to be forced down. This may have been the culprit.

    Is there a recommnended timeframe for re-cycling RSE on ZOS for preventative maintenance?

    Thanks,
    Mike P
    SECU
  • rogern
    rogern
    8 Posts

    Re: Java was started but returned exit code=1073807364

    ‏2013-03-28T19:31:59Z  
    We recycled RSE on ZOS and the problem resolved itself. When shutting down RSE, one of the services was hung and had to be forced down. This may have been the culprit.

    Is there a recommnended timeframe for re-cycling RSE on ZOS for preventative maintenance?

    Thanks,
    Mike P
    SECU
    Hi Mike,
    The next time your users experience a RDz client hang situation I would recommend generating a Java core dump for further analysis. If you are able to reproduce the client hang at will, you can use the technique below which I find to be more simple and straight forward.

    For information on how to activate, generate and collect data required to diagnose these problems, please refer to technote http://www-01.ibm.com/support/docview.wss?uid=swg21222658.
    Generating Java Core Dump (Client)
    When an Out of Memory (OOM) or hang occurs in RDz client, it's
    important to gather the Java core dump
    To update the eclipse.ini:

    1) Determine the location of the eclipse.ini by looking at the
    shortcut properties for IBM Rational Developer for System z.
    Click on Start > All Programs > IBM Softwre Delivery Platform > IBM
    Rational Developer for System z. Right-click on the shortcut for
    IBM Rational Developer for System z and select 'Properties.'

    2) Note the location of the 'Start in:' field or copy the location
    into the windows clipboard.

    3) Start up a new Windows Explorer or reuse an existing session.
    Type in the folder location or paste the location from the
    clipboard in the address field and then hit 'Enter' key. At this
    point, you should see the list of files and sub-directories
    contained in the folder.

    4) Scroll down until you see the eclipse.ini file. Make a backup
    copy on your eclipse.ini (ie. eclipse.ini.bak). After making
    backup copy, right-click eclipse.ini and select 'Edit' to open the
    file.

    5) Locate the "-vm" parm which should be near the top and replace
    the string "j9vm\jvm.dll" with "java.exe". For example,

    Before:
    -vm
    C:\IBM\SDP803\jdk\jre\bin\j9vm\jvm.dll

    After:
    -vm
    C:\IBM\SDP803\jdk\jre\bin\java.exe
    6) You can generate java core files in another directory by using
    the -Xdump option. Add this line to the bottom your eclipse.ini
    file

    -Xdump:java:label=C:\temp\javacore.%Y%m%d.%H%M%S.%pid.%seq.txt
    7) Save and close the eclipse.ini.

    8) Restart RDz to pick up the changes.

    9) When error occurs again, locate the RDz Windows command prompt
    and press CTRL+BREAK. Wait another 2 to 3 mins and CTRL+BREAK.
    Repeat previous step to capture a third dump. After collecing the
    third dump, zip up the javacore.* and attach to the PMR

    Thanks,
    Roger