Installation

This section describes known installation issues and associated solutions.

Installation shutdown hanging on some Linux systems after clicking the "Finish" button. (ID 5009728)

Description

This problem has been observed on several Linux systems. It is most common on Java Desktop System 2 but has also been observed on Linux Red Hat distributions.

After clicking the Finish button on the last installer screen, the installer fails to launch a browser window containing the product About page or product registration page, and hangs indefinitely, not returning the command prompt.

Solution

Exit the installer by pressing Ctrl+C in the terminal window in which the installer was started. After doing this, browser window containing product About page or registration page will sometimes be launched, but if it does not show up, start the browser and enter following URL in order to review About page:

file://install_dir/docs-ee/about.html

If you also selected the installation option to register the product, follow the link to registration page available on product About page.

On Windows, the imq directory needs to be created during installation. (ID 6199697)

Description

On Windows, immediately after installing Application Server Enterprise Edition, the Message Queue broker fails on startup with a message saying the directory drive:\as\domains\domain1\imq does not exist.

Note that if the broker is started after starting domain1, the directory will be created by the Application Server and the problem will not occur.

Solution

1. Create the var_home_dir_location before creating the broker:

   $imqbrokerd -varhome var_home_dir_location

   For example:

   $imqbrokerd -varhome D:\as\domains\domain1\imq

Application Server cannot be set up on RHLAS 3.0 and RHLAS 4.0 without compat-libstdc++. (ID 6396102)

Description

Installing Application Server Enterprise Edition 8.2 on a Red Hat Linux Advanced Server (RHLAS) 3.0 or 4.0 system will fail if the compat-libstdc++ library is not already installed on the system. Application Server requires t he compat-libstdc++ library on RHLAS systems, but this library is not installed by default. Note that this is only a problem on RHLAS systems.

Solution

Download and install the compat-libstdc++ RPM from http://rpm.pbone.net/index.php3/stat/4/idpl/843376/com/compat-libstdc++-7.3-2.96.118.i386.rpm.html before installing Application Server software.

lbplugin (libpassthrough.so) can not be used when server is running in 64-bit mode (ID 6480952)

Description

When running Application Server Enterprise Edition 8.2 with Web Server 7.0 in 64–bit mode, attempts to run a 64–bit version of the load balancer plugin fail with the following error:

failure: CORE2253: Error running Init function load-modules: dlopen 
of /export/home/mareks/opt/webserver7/plugins/lbplugin/bin/libpassthrough.so 
failed (ld.so.1: webservd: fatal: /export/home/mareks/opt/webserver7/plugins/
lbplugin/bin/libpassthrough.so: wrong ELF class: ELFCLASS32)
failure: server initialization failed

The problem is that there is no 64–bit load balancer plugin for Application Server Enterprise Edition 8.2, and the 64–bit Web Server requires 64–bit plugins.

You can determine whether Web Server is running in 64–bit or 32–bit mode by using the following command:

wadm get-config-prop --user=admin --config=xxx --password-file=xxx platform

Solution

No 64–bit load balancer is planned for Application Server Enterprise Edition 8.2. To work around the problem, either use the Web Server 7.0 reverse proxy feature, or configure Web Server 7.0 to run in 32–bit mode. Refer to the Web Server documentation for instructions.

Cannot run asant deploy: “The input line is too long” (Windows 2000) (ID 6485174)

Description

When installing Application Server 8.2 in the default location on Windows 2000, you may encounter the following error when running asant deploy:

$ C:/Sun/JavaES5/appserver/bin/asant deploy
The input line is too long.
The syntax of the command is incorrect.

The problem is that command lines in Windows 2000 can be no longer than 1000 characters, and depending on your system configuration, the default ANT_OPTS environment may cause the asant deploy command line to be long. This is only an issue on Windows 2000.

Solution

On Windows 2000, install Application Server in a very short directory path; for example, C:\JES5_AS).

JES5 b12, AS installation, in common.properties wrong server instance AppServer1 (ID 6485254)

Description

Using JES 5 b12 on Windows, if Application Server is selected at the top level of the select components installation panel, then the Node Agent subcomponent is also selected by default. The installation process subsequently creates a node agent and a server instance named AppServer1 that belongs to this node agent. This is the correct behavior.

However, if the Node Agent subcomponent is deselected, the installation process still creates an AppServer1 instance in the common.properties file for the domain; for example:

domain.name=domain1
appserver.instance=AppServer1

Subsequent attempts to deploy applications using asant will fail.

Solution

Edit the common.propeties file, replacing appserver.instance=AppServer1 with appserver.instance=server.

Documentation on getting a physical Connection from a wrapped Connection is no longer correct (ID 6486123)

As a result of other defects (possibly 6295215) the code provided in the Obtaining a Physical Connection from a Wrapped Connection in Sun Java System Application Server Enterprise Edition 8.2 Developer’s Guide section of Chapter 11, Using the JDBC API for Database Access, in Sun Java System Application Server Enterprise Edition 8.2 Developer’s Guide is not correct. Specifically, the line:

Connection drivercon = ds.getConnection(con);

should now read:

Connection drivercon = ((com.sun.gjc.spi.DataSource)ds).getConnection(con);

Application Server does not support NFS. (6396045)

In this version of the software, Application Server does not support Network File System (NFS).

Solution

None.