467,209 Members | 1,327 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,209 developers. It's quick & easy.

How to kill idle connections or sessions

Hi All
I came across a small doubt.
Suppose I have Max Connections parameter set to 200.
There are now 200 connections to the database.
Out of these 200 connections 50 are idle.
What will happen if a new user tries to connect to the database?
Whether he will receive error about MAXCONNECTIONS exceeded or he will be
allotted a connection as 50 agents are idle now?
Also how to kill those idle sessions or connections to make way for active
users?

Regards
Praveen

Mar 3 '06 #1
  • viewed: 6842
Share:
1 Reply
Praveen_db2 wrote:
Hi All
I came across a small doubt.
Suppose I have Max Connections parameter set to 200.
There are now 200 connections to the database.
Out of these 200 connections 50 are idle.
What will happen if a new user tries to connect to the database?
Whether he will receive error about MAXCONNECTIONS exceeded or he will be
allotted a connection as 50 agents are idle now?
Also how to kill those idle sessions or connections to make way for active
users?


Have you actually read the responses to the other threads you started?

I think you are mixing connections and db2agent processes and we would need
to know what you have in mind to be able to give you some answers.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Mar 3 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Jim G | last post: by
reply views Thread by Stefan Felkel | last post: by
4 posts views Thread by Josh Close | last post: by
4 posts views Thread by Troels Arvin | last post: by
1 post views Thread by Ming | last post: by
2 posts views Thread by Nebu Pulickal | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.