Troubleshooting Guide

Table of contents

Web Start client troubleshooting checklist

  1. Review the Web Start client information.
  2. Confirm that the Web server is available.
  3. Check the Web server configuration.
  4. Trace problems with the Web Start client.
  1. Review the Web Start client information.
    1. Review the Web Start information in the Web Start client section in the Planning, Installing, and Configuring Host On-Demand guide. This section contains important information about the Web Start client, changes for the Web server, supported JVMs, HTTPS, bookmarking, and use with Windows Restricted user computer systems.
    2. Review Web Start settings in the Host On-Demand online help.

  2. Confirm that the Web server is available.
    Depending on your configuration, the Web Start client may need to download files from the Web server to start. If you are using Telnet SSL, the Host On-Demand client may need to request additional files from the Web server when the Host On-Demand client connects to the Telnet server using SSL.

  3. Check the Web server configuration.
    Use the telnet command to check the MIME type and responses from the Web server. Keep in mind that you may not see these commands echoed back to your window. 
    telnet systemname:port 
GET /hod/filename.jnlp HTTP/1.0
    The port is 80 for Windows 2000 platforms.

    Press Enter twice.

    Look for Content-Type: application/x-java-jnlp-file to verfiy the MIME type is correct. See the following example: 

    HTTP/1.1 200 OK
Date: Wed, 08 Oct 2003 16:46:23 GMT
Server: IBM_HTTP_SERVER/1.3.26 Apache/1.3.26 (Win32)
Last-Modified: Wed, 08 Oct 2003 16:26:24 GMT
ETag: "0-755-3f843ab0"
Accept-Ranges: bytes
Content-Length: 1877
Connection: close
Content-Type: application/x-java-jnlp-file

<?xml version="1.0" encoding="utf-8"?>
<!-- Deployment Wizard Build : 8.0.0-B20030813 -->
jnlp codebase="http://arctest3.raleigh.ibm.com/hod8GM/" href="BrianDebug.jnlp">
<information>
<title>BrianDebug</title>
<vendor>IBM Corporation</vendor>
<description>Host On-Demand</description>
<offline-allowed/>
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.3+"/>
<jar href="WSCachedSupporter2.jar" download="eager" main="true"/>
<jar href="CachedAppletInstaller2.jar" download="eager"/>
<property name="hod.WSFrameTitle" value="BrianDebug"/>
<property name="hod.DocumentBase" value="http://arctest3.raleigh.ibm.com/hod8GM/BrianDebug.jnlp"
/>
<property name="hod.PreloadComponentList" value="HABASE;HODBASE;HODIMG;HACP;HAFNTIB;HAFNTAP;HATR
ACE;HAIPMON;HODAPPL;HAMACRT;HACLTAU;HODHLL;HAVT;HASLP;HAKEYPD;HA3270;HAMACUI;HAPRINT;HODMAC;HALUM;HA
3270X;HODCFG;SCCBASE;HODSSL;HA3270P;HODTLBR;HASSL;HACICS;HAFTP;HASSH;HODZP;HAHOSTG;HAPD3270;HAXFER;H
ODAPPL;HAKEYMP;HACOLOR;HODIMP"/>
<property name="hod.DebugComponents" value="true"/>
<property name="hod.DebugCachedClient" value="false"/>
<property name="hod.UpgradePromptResponse" value="Prompt"/>
<property name="hod.UpgradePercent" value="100"/>
<property name="hod.InstallerFrameWidth" value="550"/>
<property name="hod.InstallerFrameHeight" value="250"/>
<property name="hod.ParameterFile" value="HODData\BrianDebug\params.txt"/>
<property name="hod.UserDefinedParameterFile" value="HODData\BrianDebug\udparams.txt"/>
<property name="hod.CachedClientSupportedApplet" value="com.ibm.eNetwork.HOD.HostOnDemand"/>
<property name="hod.CachedClient" value="true"/>
</resources>
<application-desc main-class="com.ibm.eNetwork.HOD.cached.wssupport.WSCachedSupporter"/>
</jnlp>
    4.

  4. Trace problems with the Web Start client.
    1. To enable the Java Console and logging for the Web Start client, open the Java Web Start Application Manager and enable Web Start logging by clicking File > Preferences and then the Advanced tab on a Windows operating system. Enable the Java Console and logging.
    2. Obtain Host On-Demand basic traces that are written to the Java Console.

    Top of page Table of contents