How to kill idle connections or sessions
Question posted by: Praveen_db2
(Guest)
on
March 3rd, 2006 03:55 PM
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
1
Answer Posted
Praveen_db2 wrote:
[color=blue]
> 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?[/color]
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
|
|
|
What is Bytes?
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over 196,998 network members.
Top Community Contributors
|
