Views:

Summary


This article describes various situations when the management consoles fails to load. If you encounter problems running the management console, try the below suggestions.

 

Symptoms

1 # Unable to launch the application.

 

This error may occur after changing the master server hostname or if the .jnlp file used to launch the management console contains an unresolvable hostname for the master server.

Note that *.jnlp refers to either dpx.jnlp, nsb.jnlp, or bex.jnlp, depending on the product that you are attempting to launch.

Click Details. The following message displays and it may show the offending hostname:

Error: Unable to load resource: http://[hostname]:6122/gui/dpx.jnlp

 

2 # Problems running the Java management console, such as load library errors, can be an indication that you need to flush the Java cache.

 

 

3 # Management console crashes unexpectedly, or the management console hangs or does not respond as expected.

 

4 # Java GUI crashes when monitoring a large backup/restore job.

When monitoring a job that is backing up or restoring ~265,000 files or a 52.1 MB job log, you may experience a Java GUI crash with the default JVM heap size which is the maximum 64 MB.

 

 

Resolution

 

 

1 # Unable to launch the application.

 

 

  1. Find the *.jnlp file in the http\gui directory on the master server. If you are launching the management console from a local copy of the *.jnlp file, edit the local copy.

    Note that in this procedure, *.jnlp refers to either dpx.jnlp, nsb.jnlp, or bex.jnlp, depending on the product that you are attempting to launch.
  2. Open the *.jnlp file using a text editor.
  3. Locate the following line: <jnlp spec="1.0+" codebase="http://<server>:6122/gui" href="*.jnlp">
  4. Modify the <server> section of this line such that the new master server name or its IP address
    is contained within the <>. When running the management console on a remote machine, verify that the host name resolves to the correct IP address for the master server.

 

2 # Flush the Java cache by deleting all temporary internet files, cached objects, and applets,

On Windows machines:

 

  1. Click Start > Settings > Control Panel > Java. Click the General tab.
  2. Click Temporary Internet Files, then click the Settings button.
  3. Click Delete Files.
  4. On the Delete Temporary Files confirmation dialog box, ensure all options are selected and click OK:
  5. Then click OK on the Temporary File Settings dialog box, and then OK on the Java Control Panel dialog box. The Java management console now run properly.

3 # Turn ON advance Java Debugging.

To troubleshoot these kinds of problems, set up more advanced debugging in addition to the current debug settings provided in the Java console. Use the GUI Java Console for debugging purposes. Use this approach to get more information about the state of the Java GUI when launched through javaws.

  1. Navigate to Control Panel > Program > Java. The Java Control Panel appears.
  2. Navigate to the Advanced Tab > Java Console > Choose Show console.
  3. In the directory (by default: C:\Program Files (x86)\Java\jre6\bin) where you run javaws, create file .javawsrc (note the leading period).
  4. Place the following lines in the file:

TraceBasic=true
TraceNetwork=true
TraceSecurity=true
TraceCache=true
TraceExtensions=true
TraceTemp=true
TraceStartup=true

4. Save the file and ensure it does not have an extension.
5. Click the BEX/NSB/DPX desktop icon to launch the application. Do not start BEX/NSB/DPX locally.

The Java console opens and some debug output appear. Also, uncaught exceptions, presently hidden by javaws, also appear.

Comments (0)