Fix 3798: Unable to use more than 50% of machine memory for server
JVM settings were used by scripts when checking the validity of the instance.
This modification removes the use of the JVM setting during the bootstrapping phase.
This fixes the following issues:
* if JVM is configured for the server instance suspends on start up
for debugging, the server suspends during the bootstrapping phase
rather than when the real server instance has started. (remaining
issue related to issue 3711)
* if the JVM is configured to use more than around 45% of the
machine's memory, we run out of memory (issue 3798)
| | |
|---|
| | | OPT_CHECK_VERSION="" |
|---|
| | | fi |
|---|
| | | # Launch the CheckInstance process. |
|---|
| | | "${OPENDS_JAVA_BIN}" ${OPENDS_JAVA_ARGS} ${SCRIPT_NAME_ARG} -DINSTALL_ROOT=${INSTALL_ROOT} -DINSTANCE_ROOT=${INSTANCE_ROOT} org.opends.server.tools.configurator.CheckInstance --currentUser ${CURRENT_USER} ${OPT_CHECK_VERSION} |
|---|
| | | "${OPENDS_JAVA_BIN}" ${SCRIPT_NAME_ARG} -DINSTALL_ROOT=${INSTALL_ROOT} -DINSTANCE_ROOT=${INSTANCE_ROOT} org.opends.server.tools.configurator.CheckInstance --currentUser ${CURRENT_USER} ${OPT_CHECK_VERSION} |
|---|
| | | # return part |
|---|
| | | RETURN_CODE=$? |
|---|
| | | if [ ${RETURN_CODE} -ne 0 ] |
|---|
