1Z0-161: Oracle Java Cloud ServiceDemo

By Oracle · Question Mode

QuestionQ19

Troubleshooting and Maintenance

You are troubleshooting an application and believe the problem may be related to its use of Java Virtual Machine threads. Firewall restrictions prevent you from using web-based consoles to access WebLogic Server diagnostic data.

Which command-line operations can you use to examine the internal state of JVM threads?

  • A Log in to the Managed Server VM via SSH Run the script <wlserver_home>/server/bin/setWLSEnv.sh to set the Java classpath Run java weblogic.Admin url localhost:<listen port> -username <wluser> -password <wl passwd> GETSTATE to initiate a JVM thread dump, applying appropriate values for the arguments in angle brackets
  • B • Log in to the Managed Server VM via SSH • Use ps to determine the process id (pid) of the Java Process that is running the WebLogic instance • Run: kill-3 <pid> to output the thread dump to the stdout stream of the process
  • C • Log in to the Managed Server VM via SSH • Use the Linux command: kill –SIGDUMP <pid>, where <pid> is the process id of the JVM
  • D • Log in to the Managed Server VM via SSH
Explanation

On Linux, identifying the WebLogic Java process with ps and running kill -3 <pid> sends SIGQUIT to that JVM. The JVM writes a thread dump, containing thread stacks and states, to the process’s standard output without terminating the application.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!