• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

Database connection pooling

Hi all,

I have an application that needs to process dozens of incoming messages a second.
Each message needs to be analyzed, which requires several reads/writes to a DB2 database.

For each message that I receive, I create a thread, create and open a database connection,
do the processing and close the connection.

How can I manage the connection(s) to the database more efficiently?

Here's my connection string (just in case):
"Provider=IBMDADB2; Database = db; Hostname = 192.182.162.2; Protocol = TCPIP; Port = 50000; Uid = db; Pwd = pwd"

Any help is appreciated
0
darrgyas
Asked:
darrgyas
1 Solution
 
käµfm³d 👽Commented:
This is the preferred practice. According to documentation on IBM's website, you get connection pooling with DB2 the same as you do with other DBMSs. Even though you are creating a new connection object on demand, the underlying TCP connection isn't closed (right away). Creating a new connection object will use this TCP connection if it's available; otherwise a new connection will be created and added to the pool.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now