OES10g - How update OES Wrapper.jar for 64 and have more than 4GB of memory Limit (Doc ID 2174697.1)

Last updated on AUGUST 23, 2016

Applies to:

Oracle Entitlements Server - Version 10GR3 and later
Information in this document applies to any platform.

Symptoms

Using the OES 10gr3 with CP4 on 64 bit OS, Trying to use the 64 bit jdk on 64 bit OS and using the more than 4 GB of memory ,

Unable to start the OES admin server.

The server fails with this error:

STATUS | wrapper | 2016/02/16 01:13:34 | Launching a JVM...
INFO | jvm 5 | 2016/02/16 01:13:34 | Error occurred during initialization of VM
INFO | jvm 5 | 2016/02/16 01:13:34 | Too small initial heap for new size specified
ERROR | wrapper | 2016/02/16 01:13:34 | JVM exited while loading the application.
FATAL | wrapper | 2016/02/16 01:13:34 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2016/02/16 01:13:34 | There may be a configuration problem: please check the logs.
STATUS | wrapper | 2016/02/16 01:13:34 | <-- Wrapper Stopped
STATUS | wrapper | 2016/02/16 01:17:43 | --> Wrapper Started as Daemon
STATUS | wrapper | 2016/02/16 01:17:45 | Launching a JVM...
INFO | jvm 1 | 2016/02/16 01:17:45 | Error occurred during initialization of VM
INFO | jvm 1 | 2016/02/16 01:17:45 | Too small initial heap for new size specified
ERROR | wrapper | 2016/02/16 01:17:45 | JVM exited while loading the application.
STATUS | wrapper | 2016/02/16 01:17:51 | Launching a JVM...
INFO | jvm 2 | 2016/02/16 01:17:51 | Error occurred during initialization of VM
INFO | jvm 2 | 2016/02/16 01:17:51 | Too small initial heap for new size specified
ERROR | wrapper | 2016/02/16 01:17:51 | JVM exited while loading the application.

Changes

 

Cause

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