SDK/RTE 1.4.2.28 Release Notes
Table Of Contents
- Table of Contents
- Overview
- Features
- Installation
- Usage Documentation
- Removing support for unwanted architectures in the JRE
- Support for dynamic thread local storage (TLS)
- Signal Chaining Functionality
- Support for C++ applications built with -AA and -AP options (PA-RISC) only
- Using Java 2 JNI on HP-UX
- HotSpot JVM Options
- Garbage collectors: Parallel, Concurrent mark, and Sweep
- Allocating physical memory and swap in the Java heap
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Closing a socket when accept or read is pending (PA-RISC) - new patch information!
- Compatibility with previous releases
- Runtime Plug-In usage and configuration
- GC log-rotation support
- ThreadDumpPath support
- Additional HP and Oracle Java documentation
- Problem Fixes
- PA-RISC Known issues
- Recommend setting PTHREAD_SUSPEND_SYNC to 1 under certain conditions (HP-UX 11.31 (11i v3))
- shl_load HotSpot libjvm problem due to TLS (HP-UX 11.0 PA-RISC)
- 64-bit Support X/Motif (HP-UX 11.00 & 11.11 (11i v1) PA-RISC)
- 64-bit Support - System Call (HP-UX 11.00 PA-RISC)
- /dev/​poll Runtime Support (HP-UX 11.00 & 11.11 (11i v1) PA-RISC)
- HPjconfig Configuration Tool
- Compiler Safe Points (HP-UX 11.00 & 11.11 (11i v1) PA-RISC)
- Using Linker Option +noenvvar and +compat on HP Integrity and PA-64 Systems
- Running Java with setuid or setgid
- HP Integrity (Itanium) Known Issues
- Using pthread_suspend() under certain conditions on HP-UX 11.31 (11i v3)
- Initializing a JVM instance with JNI_CreateJavaVM or attaching to JVM with AttachCurrentThread()
- Using Linker Option +noenvvar and +compat on HP Integrity and PA-64 Systems
- Running Java with setuid or setgid
- Running Aries HP Integrity emulation on PA2.0
- Software Support
- Security fixes in the 1.4.2.28 release
charsets.jar |_________|___________|_________|________|___
jce.jar | | | |
|
jsse.jar server server server server
server
* The files for Java Web Start technology are part of the jre in the directory javaws. Web
Start release notes are also included in the javaws directory.
The tools are under opt/java1.4/bin and the libraries install under opt/java1.4/
lib. The tools.jar file contains the classes for supporting the tools and utilities. The file
dt.jar contains the DesignTime archive of BeanInfo files.
The jre directory includes the runtime environment. The file rt.jar contains the
runtime classes for the core API. The file charsets.jar contains the
internationalization and localization classes and files. The security directory contains
security management files.
The shared libraries used by the HP-UX platform are contained in the following
directories:
PA-RISC PA-RISC 1.1 32-bit
PA_RISC2.0 PA-RISC 2.0 32-bit
PA_RISC2.0W PA-RISC 2.0 64-bit
IA64N Integrity 32-bit
IA64W Integrity 64-bit
The include directory contains the header files for supporting JNI and JVMDI.
File structure Runtime Plug-in (JPI) for Mozilla
The Runtime Plug-in for Mozilla for HP-UX requires the shared library(ies) loaded by
the Mozilla browser, the remaining Runtime Plug-in files, and the RTE to be located
in the following fixed relative position:
/opt/java1.4/jre Runtime plug-in and RTE files
/opt/java1.4/jre/plugin/PA_RISC/mozilla Runtime Plug-in shared libraries loaded by Mozilla browser
/opt/java1.4/jre/plugin/IA64N/mozilla IPF Runtime Plug-in shared libraries loaded by Mozilla browser
If the JPI is installed in the default location, /opt/java1.4/jre, then the following
links are created during the installation to allow the browser to locate the Runtime
Plug-in shared library:
Runtime Plug-in PA-RISC installation:
/opt/mozilla/plugins/libjavaplugin_oji.sl -> \
/opt/java1.4/jre/plugin/PA_RISC/mozilla/libjavaplugin_oji.sl
Runtime Plug-in HP Integrity installation:
/opt/mozilla/plugins/libjavaplugin_oji.sl -> \
/opt/java1.4/jre/plugin/IA64N/mozilla/libjavaplugin_oji.sl
If the Runtime Plug-in is installed in a non-default location, the system administrator
needs to create similar links in order to enable Mozilla to find the Runtime Plug-in. Or
you may use the environment variable MOZ_PLUGIN_PATH for Mozilla.
14