Configuration and Administration

glog.local Properties

To control the behavior of Oracle Transportation Management, you can change settings in the glog.properties file or the appropriate property set.

Property

New in Version

Definition

glog.local.avoidPofOnLocalCalls

6.4.3

If true, this property avoids serialization overhead when making J2EE calls local to a single server. If serialization errors are intermittently occurring in a scalable environment, setting this property to false can aid in root cause diagnosis by forcing serialization whether J2EE calls are local or remote.

glog.local.allowHold.EntityGets

glog.local.allowHold.FinderResults

glog.local.allowHold.Managers

25A

Determines whether connections are optimized for the specified use case.

The optional feature, MINIMIZE VPD DATABASE ROUNDTRIPS ON READ,  enables the following properties to minimize VPD calls into the database for multi-layered read operations:

  • glog.vpd.maintainState=true
  • glog.vpd.optimizeDefaultUserRoleRestore=true
  • glog.local.defaultTransactionAttribute=Hold
  • glog.local.allowHold.EntityGets=true

These optimizations are enabled by default. They significantly help performance without any observed impact on functional behavior. If you think the optimizations are impacting your solution, opt out of the optional feature to confirm the difference. Then contact Support to report any differences observed. If you already set these properties in the CUSTOM property set, opting out MINIMIZE VPD DATABASE ROUNDTRIPS ON READ will have no impact unless the properties are also removed from the CUSTOM set.

glog.local.debug

6.3

Allows logging of low-level activity in the "local" container. You can debug the following: method, transaction, synchronization, and jts by defining them in this property.

 For debugging to be logged you must have the Local log ID set.

glog.local.defaultTransactionAttribute 25A

Optimizes round trip calls to the database at the cost of holding connections longer for various actions. If set to Hold, round-trip calls to the databases are optimized. If set to NotSupported, legacy behavior is maintained. Default: NotSupported.

The optional feature, MINIMIZE VPD DATABASE ROUNDTRIPS ON READ,  enables the following properties to minimize VPD calls into the database for multi-layered read operations:

  • glog.vpd.maintainState=true
  • glog.vpd.optimizeDefaultUserRoleRestore=true
  • glog.local.defaultTransactionAttribute=Hold
  • glog.local.allowHold.EntityGets=true

These optimizations are enabled by default. They significantly help performance without any observed impact on functional behavior. If you think the optimizations are impacting your solution, opt out of the optional feature to confirm the difference. Then contact Support to report any differences observed. If you already set these properties in the CUSTOM property set, opting out MINIMIZE VPD DATABASE ROUNDTRIPS ON READ will have no impact unless the properties are also removed from the CUSTOM set.

Related Topics