Connection Pool technology and its impact-zt

Yesterday, I was asked the following question: this often happens on their SQL Server servers. The number of processes at a certain point in time can reach hundreds at once. The possibility of being attacked was ruled out. I helped them analyze the possibility that the connection pool was improperly used in the application. Their programs are jsp and run through the tomcat server.

I have also introduced the connection pool technology in some special documents. Let's take a few more pictures to illustrate.

[Note] the connection pool technology is mainly used for some applications that frequently access the database. This technology can improve the reuse of connections without the need to constantly open and close connections.

 

It is easy to enable the connection pool for a connection, as shown in.

 

It is worth mentioning that I have checked some information and the tomcat server can enable the connection pool directly on the server through configuration, which is an advantage over IIS.

You can refer to the following link to learn how to configure the connection string in tomcat and enable the connection pool.

Http://www.javaeye.com/topic/25161

 

 

After the program enters the debugging status, you can see a batch of connections (20) on the server side, instead of a connection being established.

 

20 processes can be clearly viewed through the dynamic management view.

 

Http://www.cnblogs.com/chenxizhang/archive/2009/05/16/1458369.html