IBM Support

HotSpot compiler configuration causing error

Troubleshooting


Problem

HotSpot compiler configuration causing error

Symptom

If you have installed Tomcat 5 using the *.exe distribution, the installation process will setup Tomcat to use the JVM’s server mode as default (equivalent to running Java as “java –server …”).
The error will likely to occur around the DsSchemaLoader class.

Error Message

com.comergent.api.dataservices.DataServicesException: [CMGT_E_MISSING_KEYFIELD_DEFN] error: "OILHeaderKey is not defined as KeyField in DataObject: BillOrderAddress "
at com.comergent.dcm.dataservices.RelationShipInfo.buildChildJoinCriteria(RelationS hipInfo.java:535)
at com.comergent.dcm.dataservices.DsSchemaLoader.loadDataObject(DsSchemaLoader.java :1319)
at com.comergent.dcm.dataservices.DsSchemaLoader.loadInheritableDataObject(DsSchema Loader.java:1598)

Resolving The Problem

You have two options at this point:

1.Switch back to the “client” mode. To do this, select the menu item “Configure Tomcat”, then go to the “Java’ tab, then use the file browser to select the jvm.dll under the “client” directory.

2.OR run in “server” mode but use file “.hotspot_compiler” to disable the JIT compilation for class DsSchemaLoader.

One way to verify the JVM’s mode at runtime is to look for the following entry in the debs log file:

2005.07.28 14:02:29:562 Env/Thread-1:INFO:InitServlet java.vm.name: Java HotSpot(TM) Server VM
*** For the server mode

2005.07.28 14:02:29:562 Env/Thread-1:INFO:InitServlet java.vm.name: Java HotSpot(TM) Client VM
**** For the client mode

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"MCS","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

NFX6769

Product Synonym

[<p><b>]Severity[</b><p>];Normal

Document Information

Modified date:
16 June 2018

UID

swg21551700