NonStop Server for Java 7.0 Programmer's Reference

1. Export DUMP_CORE=1.
2. Start the Java application.
3. Press Ctrl+break while the process is running.
Saveabend file generation
If distributed GC is enabled, then the saveabend files are generated differently. The Java process
or GC process can encounter a problem and terminate abnormally. When one process in the Java
process group terminates abnormally, then the other processes detect the abnormal termination
and also terminate abnormally.
The first process that terminates abnormally dumps the entire user address space (full dump), and
the other processes do the partial dump of the address space. To analyze the problem, load the
saveabend file independently in eInspect for analysis. As the partial snapshot files do not
contain all the data, the full dump needs to be used to get the data.
CAUTION: The saveabend flag must be turned on for both Java launcher executable file and
the javagc executable file for creation of saveabend files for both the Java and GC processes.
You can collect the snapshot files of the Java process and GC process and send it to HP support
for analysis. You must collect all the saveabend files.
FastExec option support
For applications that use the Runtime.exec method to create a child process, NSJ7 provides a
faster method to create a child process using the -Dnsk.java.fastExec=true option. The
Runtime.exec method forks a child process and overlays its image with the new executable.
Forking the child process duplicates the parent process image, which is discarded when the exec
is executed. The -Dnsk.java.fastExec=true option builds the child process image from the
executable. It does not inherit the parent process image, thus reduces the time required to create
a child process.
Java authentication and authorization service
The Java Authentication and Authorization Service (JAAS) is integrated in NSJ7. JAAS augments
the core Java 2 platform which facilities to authenticate and enforce access controls. JAAS has the
ability to enforce access controls based on who runs the code.
JAAS implements a Java version of the standard Pluggable Authentication Module (PAM) framework.
This plug ability permits applications to remain independent from underlying authentication
technologies. New or updated authentication technologies can be plugged in without requiring
modifications to the application. Applications enable the authentication process by instantiating
a LoginContext object, which in turn references a configuration to determine the authentication
technology, or LoginModule, that is to be used in performing the authentication. The
LoginModule interface provides developers the ability to implement different kinds of authentication
technologies that can be plugged in an application.
For example, one type of LoginModule might perform a username and password based form
of authentication. Other LoginModules might involve more sophisticated authentication
mechanisms.
NSJ7 product includes LoginModule interfaces implemented by Oracle, such as
JndiLoginModule and KeyStoreLoginModule, but does not provide a LoginModule that
interfaces to the Safeguard subsystem on NonStop systems. You can also develop your own
LoginModule implementation.
For more information on writing a LoginModule implementing an authentication technology, see
JAASLoginModule Developer's Guide.
46 Implementation specifics