Observed many SEGV/FLTBOUNDS signals generated from JVM in running benchmark for
Java application of ISV and those signals seem to be related to few methods.
So, it may be possible to boost the performance by implementing JVM
as more suitable for the application.
The benchmark environment is v20z/Solaris9/Java_1.4.2_04.

[SEGV]

The Java application is huge cpu intensive one and tried truss to JVM running
the application. Then, saw huge number of SEGV in the truss output,
it's about 6000 in about 80 seconds running.

truss -c -p 18000
^Cfaults -------------
FLTBOUNDS 6332
total: 6332

signals ------------
SIGSEGV 6332
total: 6332
<snip>

[NullPointerException]

And guess the SEGV/FLTBOUNDS cames from Null Checking mechanism for NullPointerException
then tried java studio debugger to identify where NullPointerException is generated
and found only few methods are related to the exception.