Connection session is not closing on Oracle data base

Get new comments by email
You can cancel email alerts at anytime.
Comments (5)

rakesh in Bow, United Kingdom

87 months ago

On database sever lot of INACTIVE database connection sessions are still open from last 2 days .
And Aged timeout on websphere is 0 .Is it the reason behind this problem?
In our code we have closed all ResultSet,Statement , Connection objects.
All server settings for datasource are fine, which are as below

1. Connection timeout
1000 s.

2. Maximum connections
30

3. Minimum connections
7

4. Reap time
180

5. Unused timeout
2000

6. Aged timeout
0

7. Statement cache size
100

8. Purge policy
entire pool

Could you please suggest me on this issue.

- Was this comment helpful? Yes / No Reply - Report abuse

SD in Bridgewater, New Jersey

80 months ago

rakesh in Bow, United Kingdom said: On database sever lot of INACTIVE database connection sessions are still open from last 2 days .
And Aged timeout on websphere is 0 .Is it the reason behind this problem?
In our code we have closed all ResultSet,Statement , Connection objects.
All server settings for datasource are fine, which are as below

1. Connection timeout
1000 s.

2. Maximum connections
30

3. Minimum connections
7

4. Reap time
180

5. Unused timeout
2000

6. Aged timeout
0

7. Statement cache size
100

8. Purge policy
entire pool

Could you please suggest me on this issue.

When I faced a similar issue, I changed the min connection to 0, since the application was small enough to be able to afford a new connection everytime connections in the pool went back to 0.

- Was this comment helpful? Yes / No Reply - Report abuse

Venkat in Melbourne, Australia

74 months ago

rakesh in Bow, United Kingdom said: On database sever lot of INACTIVE database connection sessions are still open from last 2 days .
And Aged timeout on websphere is 0 .Is it the reason behind this problem?
In our code we have closed all ResultSet,Statement , Connection objects.
All server settings for datasource are fine, which are as below

1. Connection timeout
1000 s.

2. Maximum connections
30

3. Minimum connections
7

4. Reap time
180

5. Unused timeout
2000

6. Aged timeout
0

7. Statement cache size
100

8. Purge policy
entire pool

Could you please suggest me on this issue.

Hi Rakesh,

How did you resolve this issue.
I am encountering the same problem here. I need to close the sessions that are inactive once the connection is closed.

Thanks in advance,
Venkat

- Was this comment helpful? Yes / No Reply - Report abuse

Rakesh in Pontiac, Michigan

74 months ago

Hi Venkat,

After some analysis we have found out that database connection was not closed from some part of our appliaction.To identify this we have checked which query has been fired by the opened connection and searched that which part of our application is executing this query.We seen that connection wasn't closed at that part of application and after closing these connection we have resolved this issue.Because there is no other way that server will not close open session.

- Was this comment helpful? Yes / No Reply - Report abuse

hanu in Bangalore, India

63 months ago

i need connection poll infornmation

- Was this comment helpful? Yes (4) / No (6) Reply - Report abuse

» Sign in or create an account to comment on this topic.