The intradoc.cfg JDK_custom Variable Is Ignored Leaving UCM to Use the Incorrect JVM

(Doc ID 1520647.1)

Last updated on FEBRUARY 05, 2018

Applies to:

Oracle WebCenter Content - Version to [Release 10gR3]
Oracle WebCenter Content: Records - Version to [Release 10gR3]
Information in this document applies to any platform.


 After setting the correct new Java Virtual Machine (JVM) path in the <ucm install or cluster root>/bin/intradoc.cfg using the new 10g variable "JDK_custom" and restarting the UCM server, the new JVM is still not used.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms