Shulou(Shulou.com)06/02 Report--

Today, I will talk to you about how to analyze ServletQueryForConnPool testing. Many people may not know much about it. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

one。 Test case ServletQueryForConnPool version

1. Structure diagram

two。 Code implementation structure

3. Run time sequence diagram

4. Test run description

4.1 Database connections and database cursors may have a large footprint

Because the query and paging of the database use JDBC directly, and the paging is implemented in the form of RseultSet query result set-cursor, and each customer corresponds to a session, each session corresponds to a database connection and a result set (cursor), the database connection and cursor are released at the end of the session. Therefore, during the request process of multiple customers, the access resources of the database (database connections and cursors for data operations) may be relatively large.

Therefore, database access and its database processing may be a bottleneck.

4.2 issues where resources are not released

The database connection and cursor corresponding to the session may not be released at the end of the session.

In order to better reflect the advantages of using the Web container database connection pool, the "inactivity timeout" of the connection object in the connection pool should be set reasonably, and the secondary value and the session timeout length of the Servlet object are recommended.

5. Instructions for this test case operation

5.1 location of deployed packages:

ServletQueryForConnPool.war

5.2 deployment

1. Deploy this package through Weblogic's console tools

two。 For related parameters, please see the corresponding servlet configuration parameters in the configuration file web.xml in the ServletQueryForConnPool.war package.

5.3 testing URL

Http://server/ :port/WebAppName

That is:

Http://web/ server name: Port / application name for Servlet deployment

two。 Test case ServletQueryForConnPool_cache version

1. Structure diagram

Same as "one: test case 3"

two。 Code implementation structure

3. Run time sequence

Description: use the fourth paging query technology of "caching the result set of a SQL query", that is, a SQL query, save the results from the database query to the session, and the future customer paging query operations are obtained from this cache.

4. Test run description

Because the result set is cached, the memory requirement of the Web container server is relatively high. During the testing, the memory problem of the Web container server may affect the response performance of the whole system.

5. Instructions for this test case operation

5.1 location of deployed packages:

ServletQueryForConnPool_cache.war

After reading the above, do you have any further understanding of how to analyze ServletQueryForConnPool testing? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.