Download IBM.C9510-401.ActualTests.2018-12-19.46q.tqb
| Vendor: | IBM |
| Exam Code: | C9510-401 |
| Exam Name: | IBM WebSphere Application Server Network Deployment V8.5.5 and Liberty Profile, System Administration |
| Date: | Dec 19, 2018 |
| File Size: | 568 KB |
Demo Questions
Question 1
An application deployed to a multi-node cluster is reported to have slowness and hung threads. A system administrator is asked to review the logs on each node and identify if the hung threads are a false alarm.
How can the administrator determine that the hung threads are a false alarm?
Analyze the:
- ffdc logs
- SystemErr.log
- SystemOut.log
- native_stderr.log
Correct answer: C
Explanation:
Problem(Abstract) The SystemOut.log contains a WSVR0605W message, also called a hung thread message. A javacore, or thread dump on Solaris and HP-UX, is needed in order to determine how to resolve the potentially hung threads. Cause WebSphere Application Server attempts to report potentially hung threads using the hung thread detector. Depending on how the hung thread detector policy is configured, a thread running for a certain interval (default 10 minutes) might be reported as hung and a WSVR0605W message is printed in the SystemOut.log file:WSVR0605W: Thread <threadname> has been active for <time> and may be hung. There are <totalthreads> in total in the server that may be hung.References: https://www-01.ibm.com/support/docview.wss?uid=swg21448581 Problem(Abstract)
The SystemOut.log contains a WSVR0605W message, also called a hung thread message. A javacore, or thread dump on Solaris and HP-UX, is needed in order to determine how to resolve the potentially hung threads.
Cause
WebSphere Application Server attempts to report potentially hung threads using the hung thread detector. Depending on how the hung thread detector policy is configured, a thread running for a certain interval (default 10 minutes) might be reported as hung and a WSVR0605W message is printed in the SystemOut.log file:
WSVR0605W: Thread <threadname> has been active for <time> and may be hung. There are <totalthreads> in total in the server that may be hung.
References: https://www-01.ibm.com/support/docview.wss?uid=swg21448581
Question 2
A system administrator suspects that the slow performance of an application might be caused by lock contention.
To debug this further, what can the administrator do using IBM Support Assistant?
- Analyze the running server using IBM Monitoring and Diagnostic Tools for Java – Health Center.
- Collect a javacore and analyze it using IBM Monitoring and Diagnostic Tools for Java – Health Center.
- Collect three thread dumps at equal time intervals and analyze them using IBM Monitoring and Diagnostic Tools for Java – Dump Analyzer.
- Collect three system dumps at equal time intervals and analyze them using IBM Monitoring and Diagnostic Tools for Java – Memory Analyzer.
Correct answer: A
Explanation:
The IBM Monitoring and Diagnostic Tools for Java - Health Center is a lightweight tool that monitors active IBM Virtual Machines for Java with minimal performance overhead. The Health Center suggests live tuning recommendations for Garbage Collection, profiles methods including call stacks, and highlights contended locks. This information can help you optimize performance, improve stability and optimize system resource usage. The tool is provided in two parts:An agent, which collects data from a running application. Java applications are monitored by the Health Center agent The Health Center client, an Eclipse-based GUI which connects to the agent. The client interprets the data that is obtained by the agent and provides recommendations to improve the performance of the monitored application. The client is available as an Eclipse plug-in and as part of IBM Support Assistant (ISA). References: https://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/homepage/plugin-homepage-hc.html The IBM Monitoring and Diagnostic Tools for Java - Health Center is a lightweight tool that monitors active IBM Virtual Machines for Java with minimal performance overhead. The Health Center suggests live tuning recommendations for Garbage Collection, profiles methods including call stacks, and highlights contended locks. This information can help you optimize performance, improve stability and optimize system resource usage.
The tool is provided in two parts:
- An agent, which collects data from a running application. Java applications are monitored by the Health Center agent
- The Health Center client, an Eclipse-based GUI which connects to the agent. The client interprets the data that is obtained by the agent and provides recommendations to improve the performance of the monitored application. The client is available as an Eclipse plug-in and as part of IBM Support Assistant (ISA).
References: https://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/homepage/plugin-homepage-hc.html
Question 3
A system administrator was asked by the development team to inform them of any warning message which contains a string “Connection” on a WebSphere Application Server with High Performance Extensible Logging (HPEL) enabled.
What should the administrator do to continuously monitor logs for the required message?
- Configure log detail levels to include filter on “Connection” string.
- Use the Log Viewer in the administrative console with filter on “Connection” string.
- Use the logviewer.sh or logviewer.bat command with appropriate options.
- Use the Log Viewer in the administrative console with filter on “Connection” string and enable the “Refresh automatically” feature.
Correct answer: C
Explanation:
The High Performance Extensible Logging (HPEL) facility writes to the log and trace repositories in a binary format. You can view, query and filter the repository using the LogViewer command. logviewer.sh -monitor -includeLoggers Connection -monitor [integer] Specifies that you want the logViewer to continuously monitor the repository and output new log record entries as they are created. You can provide an optional integer argument after this parameter to specify how often you want the LogViewer tool to query the repository for new records. By default the logViewer queries the repository for new records every 5 seconds. When used with other filtering options, only those new records that match the filter criteria are displayed. References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rtrb_logviewer.html The High Performance Extensible Logging (HPEL) facility writes to the log and trace repositories in a binary format. You can view, query and filter the repository using the LogViewer command.
logviewer.sh -monitor -includeLoggers Connection
-monitor [integer]
Specifies that you want the logViewer to continuously monitor the repository and output new log record entries as they are created. You can provide an optional integer argument after this parameter to specify how often you want the LogViewer tool to query the repository for new records. By default the logViewer queries the repository for new records every 5 seconds. When used with other filtering options, only those new records that match the filter criteria are displayed.
References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rtrb_logviewer.html
