A system administrator needs to trigger a javacore only when a Java. net.
SocketTimeoutException is encountered in real time.
What does the administrator have to configure to trigger the javacore dump?
A.
Configure the JAVA_DUMP_OPTS environment variable to capture javacore for ANYSIGNAL
and all exceptions.
B.
Configure an -Xdump:java Generic JVM argument on WebSphere Application Server with the
filter for java.net.SocketTimeoutException.
C.
Code wsadmin script to capture javacore and then execute it after the
Java.net.SocketTimeoutException has been encountered.
D.
Use the log filter in HPEL to monitor forjava.net. SocketTimeoutException and then gather a
javacore dump from the Integrated Solutions Console (ISC).
Explanation:
Reference:http://publib.boulder.ibm.com/infocenter/javasdk/tools/index.jsp?topic=%2Fcom.ibm.jav
a.doc.igaa%2F_1vg00014884d287-11c3fb28dae-7ffc_1001.html
I think is B. Can someone confirm this ?
0
0
I think is A, but the variable is ONANYSIGNAL not for ANYSIGNAL then i am confused
0
0
This seems to support A or B. A may be too generic since we only want to trigger a javacore under a certain exception which may mean it should be B… Thoughts?
http://www-01.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.zos.70.doc/diag/tools/dumpagents_env.html?cp=SSAW57_8.5.5%2F9-5-7-2-2-7&lang=en
0
0
I think is C
you can run a script to capture error with wsadmin script, in this case the administrator is ask to triger javacore dump when java.net.socketTimeoutException is appear
0
0
Difficult: A might be right, but in my opionin it is to generic and the dump might not be triggered from Java. net.SocketTimeoutException even if “all exceptions” is used. From what i know this means: A fatal native exception occurs in the JVM (not a Java Exception).
Guess its B and something like that:
-Xdump:java:events=throw,filter=*InvalidArgumentException#MyApplication.*
0
0
The -Xdump option on the command line is the preferred method for producing dumps. Answer B.
http://www-01.ibm.com/support/knowledgecenter/SSYKE2_5.0.0/com.ibm.java.doc.diagnostics.50/diag/tools/dumpagents_env.html
0
0
b
0
0
Answer should be B. A is more generic
For e.g
-Xdump:java:events=throw,filter=java/lang/OutOfMem* # prefix
0
0
to generate a javacore when a a certain exception is thrown (com.my.exception.class in this case) set the following user-defined environment variable (via ACE or CF):
Name: IBM_JAVA_OPTIONS
Value: -Xdump:java:events=throw,filter=com/my/exception/class -Xdump:tool:events=throw,filter=com/my/exception/class,opts=ASYNC,exec=”/app/.liberty/bin/server dump defaultServer” -Xdump:what
0
0
answer B
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/advanced_xdump_options_to_create_javacore_and_system_dump_for_java_exception_troubleshooting?lang=en
In order to capture Javacore and System dump at the top method (my/test/ExcepTest3$ExceptionCache.) when the Java exception is thrown, we can use a customized -Xdump option to update default dump settings by setting the method name with a hash (#) separator as below:
-Xdump:java+system:events=throw,filter=java/lang/NullPointerException#my/test/ExcepTest3$ExceptionCache.,range=1..2
JVM will create Javacore (javacore.*.txt) and System dump (core.*.dmp) at the next exception occurrence. The ‘events=throw’ is an event trigger when an exception is thrown during JVM operation
0
0