Chapter 5 Installation FAQs and Troubleshooting

Chapter 5
This section lists some common errors along with their causes and solutions.
Frequently Asked Questions
What should I do if JVM crashes when I run the installer?
The installer first extracts the bundled JVM into a temporary area and then uses it to launch itself. If for some reason, the JVM crashes, you could still run the installer using another JVM, preferably JVM 1.4.2 or higher. The syntax is:

 
TIB_be-simple_3.0.1.0.exe -is:javahome C:\j2sdk1.4.2
      UNIX_package_name.bin -is:javahome /opt/jre142

 
The javahome directory must contain bin/java.exe or bin/java.
The installer will use the externally supplied JRE to launch itself.
Why and how should I set the DISPLAY variable on UNIX Platforms for GUI mode?
The installer on UNIX must open an additional window, generally for graphics. It uses the DISPLAY environment variable to tell it on what computer to open the window. If the environment variable is not set, the installer will either wait or abort after displaying:

 
      InstallShield Wizard
      Initializing InstallShield Wizard...
      Preparing Java(tm) Virtual Machine...
      ...................................
      ...................................
      ........

 
The DISPLAY variable must be set to the IP address or name of the computer (on which the installer graphics window are to be displayed), followed by a screen address, which can be :0.0 as shown in the following example:

 
      # Bourne shell
      DISPLAY=ip_address:0.0; export DISPLAY
      # Korn shell
      export DISPLAY=ip_address:0.0
      # C-shell
      setenv DISPLAY ip_address:0.0

 
For example, consider a scenario where you need to install TIBCO BusinessEvents on a remote HP-UX machine (named itaska). Because you have a Solaris 5.6 machine (named alaska) that has a video card and monitor installed, you can run an X-window application on it. So you decide to telnet to itaska from alaska.
When you telnet to itaska, you will not get access to itaska's monitor and will be unable to display an X-window application. That is why you must set the DISPLAY variable, which instructs the X-server to redirect all windows to the computer set in the variable. Before doing so, the computer (specified in the DISPLAY variable) must give permissions to share its monitor.

 
alaska> xhost + # give permission for all to its share monitor
alaska> telnet itaska
Welcome to HPUX itaska 11.00
User:
Password:
itaska> export DISPLAY=alaska:0.0 # set display on alaska
itaska> tar -xvf TIB_tra-suite_5.3.0_h7_11.tar

 
What is uninst2 directory?
If the original uninstall directory is in use at uninstall time, it cannot be removed by the installer program. The installer then creates a second uninstall directory for the second installation. To remove the second installation, you must run the uninstall program from the second uninstall directory. The original uninstall directory can also be manually removed, if empty.
Running Out of Disk Space
The installer calculates the disk space required in product home location for the selected components. The calculation is done before the actual installation (copying of files to system) begins. The installer will proceed only if sufficient free disk space is available in product home location.
However, if disk space is consumed by another process while the installer is copying the files, and if the required disk space is thereby reduced, the installer may fail and will then give a failure message.
Solution
While performing installation, avoid running other processes that consume disk space in product home location.
Configuration Errors in 64-bit Environment
Error message
If you have not performed configuration for 64-bit environments, and you have installed the 64-bit version of TIBCO Runtime Agent, you see errors such as the following.

 
Lib name /space/users//tra550/tibco/jre/1.5.0/lib/sparc/client/libjvm.so
Failed to load shared library, library name : /space/users//tra550/tibco/jre/1.5.0/lib/sparc/client/libjvm.so

Solution
Perform the configuration explained in Configuration for 64-bit Mode.
Installation Errors on HPUX 11.00 64-bit Platform
Error message
Installation on a HPUX 11.00 64 bit system may crash with the following error message:
 
Pid nnn killed due to trashed stack.
Pid nnn was killed due to failure in writing the signal context.
This happens only on HPUX 11.00 64 bit systems. It does not happen on HPUX 11.00 32 bit system and HPUX 11.11 (or 11.i) system.
To determine the OS version on your system, run:
 
uname -a
To determine the kernel bits on your system, run:
 
getconf KERNEL_BITS
Resolution
HPUX kernel patch PHKL_27282, resolves the above crash.
To determine if your system has the kernel patch, run:
 
/usr/sbin/swlist -l product PHKL_27282
or
 
what /stand/vmunix | grep PHKL_27282
If your system is an HPUX 11.00 64 bit system and it does not have the patch, first install HPUX kernel patch PHKL_27282 and then proceed with the installation. Installation of patch PHKL_27282, will reboot your system.