Skip to main content
NetApp Knowledge Base

SMSAP Java is not terminating after backup job completes

  1. Last updated
  2. Save as PDF
Views:
91
Visibility:
Public
Votes:
0
Category:
snapmanager-for-sap
Specialty:
legacy
Last Updated:

Applies to

SMSAP 3.4.2P4

Issue

A fatal error has been detected by the Java Runtime Environment:

# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000213b95fa056, pid=16424, tid=0x0000000000008668
#
# JRE version: Java(TM) SE Runtime Environment (8.0_261-b12) (build 1.8.0_261-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.261-b12 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# j com.netapp.common.platform.windows.FileSystemNativeImpl.getFileSecurityDescriptor(Ljava/lang/String;)Lcom/netapp/common/platform/FileSecurityDescriptor;+0
#
# Core dump written. Default location: C:\Program Files\NetApp\SnapManager for SAP\hs_err_pid16424.mdmp

VM Arguments:
jvm_args: -Xmx160m -XX:+HeapDumpOnOutOfMemoryError -enableassertions -Djava.library.path=.\webapp\WEB-INF\native;

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.