1693118 - nw - application fails to start after switch to sap jvm 4

14.10.2012 Page 1 of 2 SAP Note 1693118 - Application fails to start after switch to SAP JVM 4 Note Language: English Version: 3 Validity: Valid Since 26.04.2012 Summary Symptom Business Suite Java applications (e.g.: CRM ISA B2B, FSCM - Biller Direct, XCM) fail to start after switching from a vendor JVM to the SAP JVM. Following exception can be found in the default trace: Caused by: java.lang.NullPointerException: while trying to invoke the method com.sap.tc.logging.Location.debugT(java.lang.String) of an object loaded from field com.sap.isa.core.logging.sla.IsaLocationSla.location of an object loaded from local variable 'this' at com.sap.isa.core.logging.sla.IsaLocationSla. debug(IsaLocationSla.java:583) at com.sap.isa.core.logging.sla.IsaLocationSla. <init>(IsaLocationSla.java:46) at com.sap.isa.core.logging.IsaLocation.getInstance(IsaLocation. java:52) at com.sap.isa.core.logging.StrutsLog.<init>(StrutsLog.java:25) ... 22 more Other terms FSCM - Biller Direct, XCM, CRM, ISA, B2B, startup fails Reason and Prerequisites The application can't cope with SAP JVM's extended exception messages and thus fails to handle exceptions properly. The application startup fails during initialization, the applications URL (e.g.: http://<hostname>:<port>/b2b/b2b/init.do) is therefore not available. Solution Add following parameter to the list of JVM parameters using the Configtool (see related notes) and restart the Java Server afterwards: -XX:-ExtendedExceptionMessages Header Data Release Status: Released for Customer Released on: 26.04.2012 08:50:33 Master Language: English Priority: Recommendations/additional info Category: Program error Primary Component: BC-JVM SAP Java Virtual Machine Secondary Components: CRM-ISA Internet Sales Valid Releases

Upload: rubenw

Post on 18-Apr-2015

29 views

Category:

Documents

3 download

Report

Download

Embed Size (px):

TRANSCRIPT

Page 1: 1693118 - NW - Application Fails to Start After Switch to SAP JVM 4

14.10.2012 Page 1 of 2

SAP Note 1693118 - Application fails to start after switchto SAP JVM 4

Note Language: English Version: 3 Validity: Valid Since 26.04.2012

Summary

SymptomBusiness Suite Java applications (e.g.: CRM ISA B2B, FSCM - Biller Direct,XCM) fail to start after switching from a vendor JVM to the SAP JVM.

Following exception can be found in the default trace:Caused by: java.lang.NullPointerException: while trying to invoke themethod com.sap.tc.logging.Location.debugT(java.lang.String) of an object loaded from field com.sap.isa.core.logging.sla.IsaLocationSla.locationof an object loaded from local variable 'this' at com.sap.isa.core.logging.sla.IsaLocationSla.debug(IsaLocationSla.java:583) at com.sap.isa.core.logging.sla.IsaLocationSla.<init>(IsaLocationSla.java:46) at com.sap.isa.core.logging.IsaLocation.getInstance(IsaLocation.java:52) at com.sap.isa.core.logging.StrutsLog.<init>(StrutsLog.java:25) ... 22 more

Other termsFSCM - Biller Direct, XCM, CRM, ISA, B2B, startup fails

Reason and PrerequisitesThe application can't cope with SAP JVM's extended exception messages andthus fails to handle exceptions properly. The application startup failsduring initialization, the applications URL (e.g.:http://<hostname>:<port>/b2b/b2b/init.do) is therefore not available.

SolutionAdd following parameter to the list of JVM parameters using the Configtool(see related notes) and restart the Java Server afterwards:

-XX:-ExtendedExceptionMessages

Header Data

Release Status: Released for CustomerReleased on: 26.04.2012 08:50:33Master Language: EnglishPriority: Recommendations/additional infoCategory: Program errorPrimary Component: BC-JVM SAP Java Virtual Machine

Secondary Components:CRM-ISA Internet Sales

Valid Releases