IBM Support

Problems with IBM Host On-Demand 10 clients with Sun(SM) Java™ Runtime Environment 1.6.0_05 and 1.6.0_06

Troubleshooting


Problem

IBM Host On-Demand Client Issues and Workarounds using the newest levels of Sun(SM) JRE™ 1.6.0_05 and 1.6.0_06

Resolving The Problem

Two different problems have been reported by customers when using Sun JRE 1.6.0_05 and 1.6.0_06 on Host On-Demand client machines.

1) The first issue occurs with a cached client after upgrading to Sun JRE 1.6.0_05 or 1.6.0_06. Upon accessing the Host On-Demand URL with Internet Explorer 7 and starting the download of a cached client, the browser will disappear or crash. A PID file is written to the desktop if running on a Microsoft® Windows® Operating system. The PID file will reference kernel32.dll as the dll active during the crash.

This problem has been reported to Sun Microsystems as a bug. Sun reports that this has been corrected in their 1.6.0_10 pre-release version, called Java SE Runtime Environment 6u10. Sun has more current versions of 1.6 available on their site which can be downloaded from here.

In addition, a Host On-Demand workaround exists for this problem that may resolve this for some clients. The html on the Host On-Demand server used to access the cached client needs to be edited by the Host On-Demand Administrator. Edit the html file on the Host On-Demand server with a text editor and comment out the following lines in the HodCachedParms.js which is located in the Host On-Demand publish directory. Find these lines and use the // to comment out:

//if (useLegacyLifecycle)
// fs += '<PARAM NAME="legacy_lifecycle" VALUE="true">\n';

Please note that there can be undesirable effects of this change. The browser's back button may not function with this URL after this change and menu functions may not be selectable.


2) The second problem can be seen when a download client is used with Sun JRE 1.6.0_06. Any SSL or TLS download client using this JRE fails to connect using a secure connection. Cached clients can connect successfully and any client using any a JRE version lower than 1.6.0_06 will work. Sun has recognized this as a problem in this release and information can be found in the Sun bug located Here.

For this particular problem, there is no Host On-Demand workaround other than regressing to an earlier version of the JRE or using the cached client instead of the download client.

This issue is resolved in release of Sun JRE 1.6.0_07.

Another possible resolution to both of these issues is to use the IBM JRE 1.5 that is included with the Host On-Demand server installation found as a downloadable file through a link on your server's HODMain.html instead of the Sun JRE 1.6.0_05 or 1.6.0_06. The IBM JRE does not exhibit these issues.

If you have questions about these issues and you are running a supported version of Host On-Demand, you may contact Support to open a PMR via 1-800-IBM-SERV or open via IBMLink.

[{"Product":{"code":"SSS9FA","label":"IBM Host On-Demand"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF020","label":"NetWare"},{"code":"PF025","label":"Platform Independent"},{"code":"PF012","label":"IBM i"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Historical Number

100887

Document Information

Modified date:
19 April 2021

UID

swg21308627