Problem Note 49974: A "fatal error has been detected by the Java Runtime Environment ..." error occurs when using SAS® Size Profiling
 |  |  |  |
SAS Size Profiling causes JVM to fail when using the default JAVA version jdk1.6.0_30 that is required for SAS 9.3 TS1M2. Errors similar to the following are displayed in the Jboss log:
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000000800000009, pid=26601, tid=1169295680 # # JRE version: 6.0_30-b03 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C 0x0000000800000009 float+0x2aab1009 # # An error report file with more information is saved as: # /xxx/sfw/jboss/jboss-4.2.3.GA/bin/hs_err_pid26601.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # *** JBossAS process (26601) received ABRT signal ***
Follow the steps below to work around the issue:
- Replace JAVA version jdk1.6.0_30 with version jdk1.6.0_21.
In the file ".../jboss-4.2.3.GA/bin/SASServer1.sh", set environment variable "JAVA_HOME" to the location where jdk1.6.0_21 was installed.
Example:
JAVA_HOME="/usr/java/jdk1.6.0_21"
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Size Profiling | Microsoft Windows Server 2003 Standard Edition | 3.2_M1 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 3.2_M1 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 3.2_M1 | 9.3 TS1M2 | ||||
| Microsoft Windows Server 2008 | 3.2_M1 | 9.3 TS1M2 | ||||
| Linux for x64 | 3.2_M1 | 9.3 TS1M2 | ||||
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2013-05-21 09:42:15 |
| Date Created: | 2013-05-17 09:37:53 |