Linux requires the following compatibility libraries:
If you are running 64-bit Linux, you must install the system libraries for 32-bit Linux.
When Sun Java System Applications Server 8.1 2005Q2 Update 2 is installed on systems running Red Hat Linux AS 2.1 or 3.0, the stack size of the threads created by the Red Hat AS operating system for Application Server is 10 MB. However, when the number of Access Manager user sessions reaches 200, this stack size causes resource contention, and the JVM either crashes or hangs.
Solution Set the stack size to 256 KB by executing the following command on the console used to start Application Server:
# ulimit —s 256;
While configuring UWC on the Linux 3.0 platform all configuration tasks are completed except for one.
Solution In order to prevent this inconsistent behavior from occurring, perform the following tasks:
1. cd to /var/opt/sun/uwc/staging.
2. Type ls —l to display the directory contents.
3. If you self reference a symbolic link, be sure to delete it before proceeding to the next step.
4. Type ./config-appserver8x deploy.
During the installation process you are prompted to enter your password. If you click the backspace key your password becomes visible (minus the last character).
JAVA_HOME is not defined correctly. This error prevents Ant from loading. This also prevents SOAR from loading since it requires Ant.
Solution In the Ant script change line 19 from no_config=false to noconfig=true.
Ant 1.6.1. (bundled with Java ES 4) searches for the following configuration files:
In order for Ant to work in Java ES correctly it needs to ignore the settings in the above listed configuration files and use the settings provided by Java ES. In order to do this, you are requested to perform the following workaround:
Solution (1) use –noconfig with ant (ant –noconfig <your command>)
Solution (2) Remove /etc/ant.conf
Java Enterprise System developers have tested with Red Hat 2.1U2 and 3.0U1. We cannot guarantee that there are no issues with later releases. Please contact your service representative for further information.
During STH stress testing tcp_smpt_server produces a core dump.
If you remove the Linux RPMs directly, the next time the installer is run, it may see Message Queue as still being installed and not behave correctly.
Solution If you have already removed the Message Queue RPMs manually, you must uninstall Message Queue using the uninstaller. Run the uninstaller and select Message Queue components for removal.
During installation, the required shared library, compat-libstdc++-7.3-2.96.122 RPM is not installed. Without the RPM, Directory Server cannot be configured.
Solution Manually install the RPM from the distribution CD.
Sometimes when a component product is installed, one of the necessary RPMs for the uninstallation, sun-entsys-uninstall-l10n-2.0-1, does not get installed.
Solution Manually install the missing uninstall RPM by doing the following:
# rpm -i sun-entsys-uninstall-2.0.i386.rpm
After installing the RPM, the uninstall script will appear.
In the Linux release of Java Enterprise System, Message Queue delivers its own copies of the NSPR (Netscape Portable Runtime) and NSS (Network Security Services) libraries. The versions installed with Message Queue are older than the versions installed by Java Enterprise System.
If Message Queue was installed in the default location, the older libraries are found in /opt/imq/lib. If you build a Message Queue C application the Message Queue C runtime library (mqcrt.so) links against the older NSPR and NSS libraries in /opt/imq/lib. While this is a supported and tested combination, it is recommended that you use the newer versions installed by Java Enterprise System in /opt/sun/private/lib.
To use the newer versions of the libraries, set the LD_PRELOAD environment variable to:
/opt/sun/private/lib/libnspr4.so:\\ /opt/sun/private/lib/libplc4.so:\\ /opt/sun/private/lib/libplds4.so:\\ /opt/sun/private/lib/libnss3.so:\\ /opt/sun/private/lib/libssl3.so
before running your Message Queue C application.
Even if installation was successful, the last installer page lists several Java exceptions and does not display a successful installation message.
Solution Ignore the error and look at the logs in /var/sadm/install/logs. The logs will reveal if the installation was successful or not.
The window for certain languages like German is not wide enough to display the entire interface. As a result, text of elements like hints get truncated at the right hand side or at the bottom.
Solution Manually resize the window.