An EJB application posts a request message into a JMS destination and waits for a response message on a different JMS destination. To correlate the response message to the request message, the application uses the JMS correlationId of the message. The application waits up to five seconds for a response before timing out the request.
A Message Driven Bean (MDB) running on a different cluster is responsible for consuming the request message, process it and post a response message.
The destinations are defined in a Service Integration Bus (SIB) within the cell.
Intermittent timeout exceptions have occurred for the requester application. How can a system administrator correlate and analyze the debug information from both requester and consumer applications?
A. Enable High Performance Extensible Logging (HPEL).
Use HPEL logViewer command to see debug information.
B. Enable a diagnostic trace in both requester and consumer servers.
Use the Integrated Solutions Console (ISC) to set the admin=all trace. Analyze the trace.
C. Enable High Performance Extensible Logging (HPEL).
Enable Cross Component Trace (XCT) to include request IDs in log and trace records. Use HPEL logViewer command with appropriate filters to see debug information.
D. Using the Integrated Solutions Console (ISC), browse the request message that has timed out and look for any key application data.
Search for exceptions using the key application data in both requester and consumer in native_stderr.log and native_stdout.log.
|
Download Printable PDF. VALID exam to help you PASS. |
 |