The stack trace can help you diagnose problems that occur when your application runs SQL statements. In a stand-alone application, the entire stack trace can be useful. In other situations, such as using JDBC to execute a query inside a servlet, the first few entries in the stack trace provide the most information regarding the origin of the SQL statements, and later stack trace entries show information specific to the Web services that relayed the request to the servlet.
pureQuery ignores this property if you are using it with the packagePrefixExclusions property. pureQuery uses the value of the latter property instead.
If you are performing incremental capture: Lowering the value of this property does not cause pureQuery to remove entries from previously captured stack traces.
이 등록 정보는 다음과 같은 값을 가질 수 있습니다.
pureQuery supports a stack trace depth of 1. However, a stack trace of this depth is not informative. The stack traces that are produced when the depth is 1 identify the JDBC method that is invoked to run an SQL statement. These stack traces do not provide information regarding where that method was invoked.