Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / March 2006

Tip: Looking for answers? Try searching our database.

How to kill idle connections or sessions

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Praveen_db2 - 03 Mar 2006 15:43 GMT
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
Knut Stolze - 03 Mar 2006 15:48 GMT
> Hi All
> I came across a small doubt.
[quoted text clipped - 6 lines]
> 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.

Signature

Knut Stolze
DB2 Information Integration Development
IBM Germany

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.