1Z0-133 practice question 6 of 25

You are running WebLogic Server under a 64-bit HotSpot JVM. You edit your domain’s setDomainEnc.sh script to update the minimum and maximum heap…

You are running WebLogic Server under a 64-bit HotSpot JVM. You edit your domain’s setDomainEnc.sh script to update the minimum and maximum heap sizes as follows: USER_MEM_ARGS=”-Xms32meg –Xmx150meg” Export USER_MEM_ARGS You try to start a managed server by running the domain start script at the command line. The server fails with the message: Invalid initial heap size: -Xms32meg Why does the server fail with that message?

Answer options

A: The minimum heap size for a 64-bit JVM is 64 Megabytes

B: For performance reasons, the minimum heap size and maximum heap size should be the same value

C: The parameter value was entered incorrectly. The correct value is: “-Xms32m –Xmx150m” Correct answer

D: The parameter value was entered incorrectly. You must enter memory parameter values in Kilobytes

E: The parameter value was entered incorrectly. The correct value is: “-Xms:32meg – Xmx:150meg”

Correct Answer:

C. The parameter value was entered incorrectly. The correct value is: “-Xms32m –Xmx150m”

Explanation

The server fails to start because the Java Virtual Machine (JVM) does not recognize the unit "meg" for specifying memory size. The error message Invalid initial heap size: -Xms32meg indicates a syntax or parsing error by the JVM when interpreting the startup parameters. The standard syntax for specifying memory in megabytes for HotSpot JVM options like -Xms (initial heap size) and -Xmx (maximum heap size) requires using the suffix m or M. The correct format should be -Xms32m and -Xmx150m.

Why Incorrect

A. There is no mandated 64 MB minimum heap size for a 64-bit JVM. The error is a syntax parsing failure, not a violation of a minimum size requirement.
B. While setting the minimum and maximum heap sizes to the same value is a common performance tuning recommendation, it is not a requirement for the JVM to start.
D. JVM memory parameters are not restricted to kilobytes. They can be specified in kilobytes (k or K), megabytes (m or M), and gigabytes (g or G).
E. The correct syntax for the -Xms and -Xmx options does not include a colon (:) between the flag and the value.

References

1. Oracle Java SE 8 Documentation

java command: "The -Xms and -Xmx options set the initial and maximum sizes of the heap. ... To specify a size in megabytes

append the letter m or M. To specify a size in gigabytes

append the letter g or G. To specify a size in kilobytes

append the letter k or K."

Source: Oracle

"java - the Java application launcher

" Java Platform

Standard Edition Tools Reference for Oracle JDK 8

Section: "Non-Standard Options".

2. Oracle WebLogic Server 12c Documentation

Performance and Tuning: The official documentation provides examples of setting the heap size

consistently using the m suffix for megabytes. For instance

it shows MEMARGS="-Xms512m -Xmx1024m". This confirms the standard JVM syntax is expected within the WebLogic environment.

Source: Oracle

"Tuning the JVM" in Tuning Performance of Oracle WebLogic Server 12.2.1.4.0

Section: "Specifying Heap Size Values".

Keep practicing

Take the free 1Z0-133 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test