HP-UX Programmer's Guide for Java 2

1. Use the option -XX:MainThreadStackSize=<value> to increase the primordial
thread stack size, However be aware that -XX options are non-standard options,
and are liable to change from release to release.
2. Use the -Xss option to set the thread stack size. This workaround may be less
desirable because -Xss sets the stack size for all threads, not just the primordial
thread. For example, if your application has 100 threads and you set the maximum
thread stack size to 4M with the -Xss option, the application would use nearly
400MB of address space just for thread stacks. If you did not use the -Xss option,
the application would have only used 50MB (512k (the default -Xss value) * 100
threads) of address and swap space.
3. Change the application so as to call JNI_CreateJavaVMfrom a non primordial
thread. That is, create a new thread with an appropriate stack size, using
pthread_create and use this new thread to initialise the JVM.
Non-Main/Primordial thread stack size limits
The default stack size for 1.4 64-bit mode threads created by the JVM is 1MB. On
PA-RISC 32 and 64-bit systems, the default stack size for threads created using the
pthread library is 64KB.
Here are some suggestions to work around stack overflow problems in threads other
than the main thread:
1. If the thread is created in native code and is attached to Java™ through
JNI_AttachCurrentThread, increase the stack size attribute when creating the
thread with pthread_create.
2. If the thread is created inside Java™ and there is a stack overflow condition, increase
the thread stack size with -Xss<n>
Dynamically loading the Hotspot JVM (SDK 1.3.1.x and 1.4.2.x PA-RISC)
Normally you would link against the JRE and use HotSpot, but sometimes you might
want to load the JVM dynamically, especially if you are integrating Java™ with legacy
applications.
(The example for Dynamically loading the Classic JRE can now be found in the
Appendix.)
Non-Main/Primordial thread stack size limits 59