Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
The moose likes JDBC and the fly likes exception while connecting to the database Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC
Bookmark "exception while connecting to the database" Watch "exception while connecting to the database" New topic
Author

exception while connecting to the database

santhoshkumar samala
Ranch Hand

Joined: Nov 12, 2003
Posts: 156

hi iam getting following exception while connecting to the database



please help me to resolve this


santhosh<br />SCJP,SCWCD
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Looks like you are trying to use more sessions than Oracle is cnfigured to allow. Do you close every Connection after you have finished with it in a finally block?


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
santhoshkumar samala
Ranch Hand

Joined: Nov 12, 2003
Posts: 156

yes.. i have closed all the connections in finally
Muhammad Saifuddin
Ranch Hand

Joined: Dec 06, 2005
Posts: 1321

Originally posted by santhoshkumar samala:






I have no major experience in Oracle but I google and found some related with your query.

hope it helps

ORA Tips


Saifuddin..
[Blog][Linkedin] How To Ask Questions On JavaRanch My OpenSource
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Originally posted by santhoshkumar samala:
yes.. i have closed all the connections in finally


Hmm. Just noticed ORA-00604 happens first. So it looks like something is using up the available sessions as a result of your application connecting. What are you doing when this error occurs? Does it happen as soon as you connect? Does your schema have a trigger associated with it?
Chris Hendy
Ranch Hand

Joined: Mar 04, 2006
Posts: 98
First find out the maximum number of sessions the database is configured to allow:

select * from v$parameter vp where lower(vp.NAME) = 'sessions';

Then look at what sessions are curently connected:

select vs.username, vs.program, vs.module,
to_char(vs.logon_time,'DD-MON-YYYY HH24:MI:SS') lt
from v$session vs
where vs.audsid <> 0

Only then can you decide if it is an application error or a misconfigured database.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: exception while connecting to the database