NoSuchFieldError, TreeMap$Entry: field left not found during installation of WebSphere Application Server V4
 Technote (FAQ)
 
Problem
When starting the installation program for WebSphere® Application Server V4.0, the installer immediately stops. It produces error text referencing a NoSuchFieldError for TreeMap$Entry field left.
 
Cause
When starting the installation program for WebSphere Application Server V4.0, the installer immediately stops and produces the following error text:


Exception in thread "main" java.lang.NoSuchFieldError:
java.util.TreeMap$Entry: field left not found at
java.util.TreeMap.put(TreeMap.java:454) at
sun.java2d.SunGraphicsEnvironment.initTerminalNames(SunGraphicsEnvironment.java:887) at
sun.java2d.SunGraphicsEnvironment.initCompositeFonts(SunGraphicsEnvironment.java:810) at
sun.awt.X11GraphicsEnvironment.initCompositeFonts(X11GraphicsEnvironment.java:402) at
sun.java2d.SunGraphicsEnvironment$1.run(SunGraphicsEnvironment.java:109) at
java.security.AccessController.doPrivileged(Native Method) at
sun.java2d.SunGraphicsEnvironment.<init>(SunGraphicsEnvironment.java:83) at sun.awt.X11GraphicsEnvironment.<init>(X11GraphicsEnvironment.java:68
at java.lang.Class.newInstance0(Native Method) at
java.lang.Class.newInstance(Class.java:254) at
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:64) at java.awt.Window.<init>(Window.java:190) at
java.awt.Frame.<init>(Frame.java:318) at
java.awt.Frame.<init>(Frame.java:265) at
MainFrame.<init>(MainFrame.java:35) at
InstallerGUI.init(InstallerGUI.java:163) at
InstallerGUI.<init>(InstallerGUI.java:153) at
WASInstaller.install(WASInstaller.java:102) at
WASInstaller.main(WASInstaller.java:291)

This error occurred in an environment in which a customer used an X Windows Server product (for example, HummingBird Exceed) on a Microsoft® Windows® 2000 system to connect to a Solaris™ system which was acting as a tunnel server. This error occurred while attempting to install WebSphere® Application Server V4 on an AIX® system.

The stack trace indicates that the problem occurs during the initialization of the X Windows client for the WebSphere Application Server V4 GUI. Notice that there are references to the Sun Java classes in the stack trace, despite the fact that the installer is using an IBM® Java™ SDK on an AIX system. In this case, a Sun Solaris system was used as a tunnel server (which was acting as the host for X Windows), and the interaction between the Solaris and AIX X Windows caused problems in the installer.

The Solaris tunnel server connected to an AIX system in such a way that the customer was able to use the AIX Common Desktop Environment (CDE) in their X Windows session. Some X Windows-enabled software products functioned correctly, but the WebSphere Application Server V4 installer software did not.

 
Solution
Bypass the AIX Common Desktop Environment (CDE)

To resolve this problem, bypass the Common Desktop Environment (CDE). In general, it is recommended that you log in to the target system using telnet (or ssh) and export the DISPLAY environment variable to the X Windows server.

Change directory to the WebSphere Application Server V4 install image, then issue the following commands:


export DISPLAY=<IP Address of X Windows server>:0.0
./install.sh

The installer will now function normally.

Silent installer

Alternatively, you can use the silent installation option for the WebSphere Application Server V4 installer. Information about the silent installer is located at:
http://publib.boulder.ibm.com/infocenter/wasinfo/topic/com.ibm.websphere.v4.doc/wasa_content/0229.html

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): HP-UX
Software version: 4.0.7
Software edition:
Reference #: 1173369
IBM Group: Software Group
Modified date: Jun 30, 2004