Java Applications Crash on T7/M7 SPARC Systems

Asset ID:	1-72-2254266.1
Update Date:	2017-11-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2254266.1 : Java Applications Crash on T7/M7 SPARC Systems

Applies to:

Java SE JDK and JRE - Version 7 to 8
SPARC T7-1 - Version All Versions and later
SPARC T7-2 - Version All Versions and later
SPARC T7-4 - Version All Versions and later
OPC SPARC T7 Compute Rack - Version All Versions and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)

Symptoms

Java applications running on T7 or M7 SPARC systems may crash in a variety of methods/tasks. Below are two examples of crash reports.

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xffffffff7d9b2bd4, pid=4599, tid=21
#
# JRE version: Java(TM) SE Runtime Environment (7.0_76-b13) (build 1.7.0_76-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.76-b04 mixed mode solaris-sparc compressed oops)
# Problematic frame:
# V [libjvm.so+0x5b2bd4] unsigned long CompactibleFreeListSpace::block_size(const HeapWord*)const+0x15c

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xfe9e33a8, pid=4089, tid=7
#
# JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
# Java VM: Java HotSpot(TM) Server VM (24.80-b11 mixed mode solaris-sparc )
# Problematic frame:
# V [libjvm.so+0x9e33a8] void objArrayKlass::oop_follow_contents(ParCompactionManager*,oopDesc*)+0xa4

Crashes have also been reported in various other methods, such as:

J 332 C2 java.util.HashMap.put()

V objArrayKlass::oop_oop_iterate_range_nv()

V oopDesc*ParNewGeneration::copy_to_survivor_space_avoiding_promotion_undo()

J 358 C2 java.util.Properties.load0()

J 484 C2 oracle.sysman.gcagent.metadata.impl.datacollection.MetadataCache.store()

J 194 C2 java.util.concurrent.ConcurrentHashMap$Segment.rehash()

j oracle.xml.parser.v2.XMLAttr.xdkGetFirstChild()

Changes

This issue most often occurs after migrating a Java application from older hardware systems, e.g. T4/T5, to T7/M7 Solaris SPARC systems, but it can also occur on new implementations of a Java application on a T7/M7 if the Java version is below Java SE 7 Update 85-b33 or Java SE 8 Update 60.

Cause

These crashes are caused by using a Java SE version that is older than the minimum certified Java version for SPARC T7/M7 systems. See the Solaris documentation:

Solution

Use a T7/M7-certified version/patch update of Java SE. The minimum certified versions/patch updates are:

Java SE 7 Update 85 b33 (non-public)¹
Java SE 8 Update 60 b27 (non-public)¹

For both security and performance reasons, it is highly recommended to use the latest patch update of the desired Java SE version¹.

¹Java SE 7 Update 80 and higher updates of Java SE 7 are non-public releases. Also, Java SE 8 Update 60 b27 (build 27) is a non-public release. Solaris users are not automatically entitled to use non-public releases of Java SE. Non-public Java SE releases require a Java SE support license for access and use with third party applications or custom applications on all platforms, including Solaris. Users of supported Oracle software applications that run with Java may also download and use these Extended Support releases, but the use is limited to only those supported Oracle software applications that require Java. This does not extend to custom client applications that are used to connect to an Oracle application. See document, Support Entitlement for Java SE when Used as Part of Another Oracle Product (Doc ID 1557737.1) for details.   The public releases which are certified for T7/M7 systems are:

      Java SE 7 - No public versions certified for T7/M7
      Java SE 8 - Java SE 8 Update 65 (public) or any higher public patch update of Java SE 8

If Java 7 is required for your custom or third party application on T7/M7 hardware, a Java SE support license is required prior to access and use Java SE 7 Update 85-b33 or higher release. Contact your account/sales team for information about obtaining a Java SE support license.

To determine the system is a T7/M7 system, run the prtdiag command as root:

root# prtdiag -v
System Configuration: Oracle Corporation sun4v SPARC T7-4
Memory size: 14336 Megabytes

================================ Virtual CPUs ================================

CPU ID Frequency Implementation Status
------ --------- ---------------------- -------
0 4133 MHz SPARC-M7 on-line
1 4133 MHz SPARC-M7 on-line
2 4133 MHz SPARC-M7 on-line
3 4133 MHz SPARC-M7 on-line
4 4133 MHz SPARC-M7 on-line
5 4133 MHz SPARC-M7 on-line
6 4133 MHz SPARC-M7 on-line
7 4133 MHz SPARC-M7 on-line
8 4133 MHz SPARC-M7 on-line
9 4133 MHz SPARC-M7 on-line
10 4133 MHz SPARC-M7 on-line
11 4133 MHz SPARC-M7 on-line
12 4133 MHz SPARC-M7 on-line
13 4133 MHz SPARC-M7 on-line
14 4133 MHz SPARC-M7 on-line
15 4133 MHz SPARC-M7 on-line

+++++++++++++++++++++++++++++

References

<BUG:25479369> - JAVA APPS ARE CRASHING QUICKLY ON M7 MACHINES
<BUG:24435131> - JAVA APPS ARE CRASHING QUICKLY ON T7 MACHINES
<NOTE:1439822.1> - All Java SE Downloads on MOS
<NOTE:1320713.1> - Data Gathering for a Java SE Collaboration Service Request
<NOTE:1318532.1> - Data Collection for Java Issues - Crash or Exception with HotSpot Error Log File
<NOTE:1274584.1> - How to Use Pkgapp to Gather Libraries to Debug Core/Gcore/Crash Files in Solaris and Linux
<NOTE:1395507.1> - Where Can I Find the Java HotSpot Fatal Error Log (hs_err_[pid] log)?

Attachments

This solution has no attachment