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 for java.net.SocketTimeoutException and then gather a javacore dump from the Integrated Solutions Console (ISC).

Dump agents are set up during JVM initialization. They enable you to use events occurring within the JVM, such as Garbage Collection, thread start, or JVM termination, to initiate one of four types of dump or to launch an external tool. Default dump agents are set up at JVM initialization They are sufficient for most cases, but the use of the -Xdump option on the command line allows more detailed configuration of dump agents. The total set of options and sub-options available under -Xdump is very flexible and there are many examples presented in this chapter to show this flexibility.

Example: To generate system cores:

-Xdump:system:events=user

References: http://www-01.ibm.com/support/docview.wss?uid=swg21242497