X-Viewer and LWST
An administrator has found some transactions with delayed response time (8 + sec). Detailed information about one of the transactions is accessed quickly using the X-Viewer and following log data was retrieved. Please see below for the actual content in the X-Viewer.
Environment: Oracle and WebSphere.
Note: Only the core content relevant for troubleshooting is shown below.
1. FILE-ROPEN
[0000] public LUnitBox getApplRealMaxSerial(LUnitBox) [2105 ms]
1][0000] FILE-ROPEN /dao/WRRA105D.class
2075][0000] FILE-ROPEN /dao/WRRK105D.class
-> FILE-ROPEN has taken more than 2 seconds to finish. Does this mean the applicable class was modified then reloaded? With default installation setting of LWST, Jennifer’s X-View shows the execution status of external resource (JDBC, File I/O, Socket I/O, ext) within each transaction.
Take a look at the log data in X-Viewer. Loading (ROPEN) WRRA105D.class took 2+ seconds. In this case, it is more likely that the 2 second was used for processing method, getApplRealMaxSerial(LUnitBox), and related logic than class being modified and reloaded. Check the method and related logic in transaction and set the LWST configuration file, then Jennifer can provide actual method name loading class file and more detailed execution time.
2. SQL script and FETCH time
[0000] public LUnitBox getApplCorpInfo(LUnitBox) [6480 ms]
[0000] public LUnitBox selJjubcorp_12(LUnitBox) [6480 ms]
GET-CONNECTION DataSource.getConnection()
SQL-PREPARE_STMT{99} [SELECT … ] [0 ms] param1:[Y,Y]
SQL-EXECUTE-QUERY{99} [1 ms] param1:[Y,Y]
param2:[‘01’,’1801’,’2007’,478]
6480][0000] FETCH [1/123]
SQL script execution time is less than 1ms, but time gap for FETCH is 6,480ms. Is there a problem with FETCH?
According to X-Viewer data, the query runtime is 1ms but fetch time of the data is about 6.4 seconds. If there is a logic between query execution and rs.next(). Configuring LWST to trace related method should identify the cause of delay between FETCH. However, if there is no logic, the cause of delay may be DB or network problem at the time rs.next() method is called to retrieve the requested value.
Please review the LWST configuration guide for detailed instruction.
http://www.jennifersoft.com:8080/man/viewer/DocumentViewer.jsp?id=626a2216-0237-483c-aaee-376cfe549252 |
