Symptom
Some of the JVM system properties have been changed and they cause different issues:
- Example 1:
The deployment is failing with error: java.lang.ClassNotFoundException: com.sun.enterprise.iiop.POAEJBORB
The reason for above error is because the system property "org.omg.CORBA.ORBClass" with default value "com.sap.engine.system.ORBProxy" was unexpectedly overwritten to "com.sun.enterprise.iiop.POAEJBORB" by a specific application or lib/service. - Example 2:
The XML parse will lead to excetion: NotSerializableException: com.sap.engine.lib.xml.parser.XMLParser
The reason of the above error is because the system property "-Dorg.xml.sax.driver" with default value "com.sap.engine.lib.xml.parser.SAXParser" was unexpectedly overwritten to "com.sap.engine.lib.xml.parser.XMLParser" by a specific application or lib/service. - Example 3:
The "user.timezone" JVM parameter does not reflect the OS settings.
You want to identify the component which changes the JVM system properties by calling either System.setProperty(String key, String value) or System.setProperties(Properties prop).
Note: To enable on the go SAP JVM tracing that does not require a server restart, check SAP KBA ##2864787 - How to enable SAP JVM trace on the fly.
Read more...
Environment
- SAP Java Virtual Machine all releases
Product
Keywords
System.setProperty,System.setProperty, System,setProperty,setProperties,com.sun.enterprise.iiop.POAEJBORB,ClassNotFoundException,NotSerializableException,com.sap.engine.lib.xml.parser.XMLParser,com.sap.engine.system.ORBProxy, com.sap.engine.lib.xml.parser.SAXParser, Xtrace, JdkInternals, NativeTracer, com.sap.jvm.impl.util, com.sap.jvm.impl.monitor.vm, PropertyTracer , KBA , BC-JVM-VM , Virtual Machine , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.