You are troubleshooting an application and suspect that the issue lies with the use of Java Virtual Machine threads. Because of firewall restrictions, you cannot use web-based consoles to access the…

Question

Options

• ALog 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 password> GETSTATE to initiate a JVM thread dump, applying appropriate values for the arguments in angle brackets
• BLog in to the Managed Server VM via SSH Use jstack to determine the process ID (pid) of the Java process that is running the WebLogic instance Run: sudo -u <pid> io.output_thread_dump to the stdout stream of the process
• CLog in to the Managed Server VM via SSH Use the Linux command: kill -SIGDUMP <pid>, where <pid> is the process id of the JVM
• DLog in to the Managed Server VM via SSH Run the java -Xcheck:jni MyApp with the verbose : gc option

• A
  17% (6)
• B
  69% (25)
• C
  6% (2)
• D
  8% (3)

No community discussion yet for this question.