Make sure your developers properly close resultsets and statements. It could be
that they remain open after exceptions. Make sure you have the closing
statements in the finally section of try/catch/finally.
hth
*
* Boris Niyazo
gt; Betreff: Re: mysteriously dying connections (Oracle <-> tomcat)
>
>
> i checked this over and over again. i really do return all the connetions.
>
> - Original Message -
> From: "Ralph Einfeldt" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
>
i checked this over and over again. i really do return all the connetions.
- Original Message -
From: "Ralph Einfeldt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 21, 2001 5:30 PM
Subject: AW: mysteriously dying connections (Oracle <->
lose();
> }
>
>-- Bill K.
>
>-Original Message-
>From: Adam Myatt [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, June 21, 2001 9:51 AM
>To: [EMAIL PROTECTED]
>Subject: RE: mysteriously dying connections (Oracle <-> tomcat)
&g
ne 21, 2001 9:51 AM
To: [EMAIL PROTECTED]
Subject: RE: mysteriously dying connections (Oracle <-> tomcat)
All right. I found the sql_text listing in the open cursor view. Is there a
sure fire way to have the cursors close when the servlet is done using
them. (And if so is using connection
]
www.filip.net
>-Original Message-
>From: Adam Myatt [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, June 21, 2001 9:51 AM
>To: [EMAIL PROTECTED]
>Subject: RE: mysteriously dying connections (Oracle <-> tomcat)
>
>
>
>All right. I found the sql_text listing in the o
ser [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 21. Juni 2001 16:38
> An: [EMAIL PROTECTED]
> Betreff: mysteriously dying connections (Oracle <-> tomcat)
>
>
> hi all!
>
> problem:
>
>
> database access is managed via a java class that is
&
All right. I found the sql_text listing in the open cursor view. Is there a
sure fire way to have the cursors close when the servlet is done using
them. (And if so is using connection pooling and closing the recordset and
statement one way?)
At 07:33 PM 6/21/2001 +0300, you wrote:
> you can
Title: RE: mysteriously dying connections (Oracle <-> tomcat)
you can use v$parameter view for getting OPEN_CURSORS paremeter value.
or in sql plus or svrmgrl type
show parameter OPEN_CURSORS
-Original Message-
From: William Kaufman [mailto:[EMAIL PROTECTED]]
Sent: Thursday
-- Bill K.
-Original Message-
From: Adam Myatt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 8:54 AM
To: [EMAIL PROTECTED]
Subject: RE: mysteriously dying connections (Oracle <-> tomcat)
Bill,
What if the V_$OPEN_CURSOR is not present in the SYS schema. Using the DBA
Studio,
olTcpConnector in your
>server.xml.
>
>-- Bill K.
>
>-Original Message-
>From: Jan M. STANKOVSKY [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, June 21, 2001 8:16 AM
>To: [EMAIL PROTECTED]
>Subject: Re: mysteriously dying connections (Oracle &l
-- Bill K.
-Original Message-
From: Jan M. STANKOVSKY [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 8:16 AM
To: [EMAIL PROTECTED]
Subject: Re: mysteriously dying connections (Oracle <-> tomcat)
Same here but we have the stopping of the tomcatserver very frequent
Same here but we have the stopping of the tomcatserver very frequently.
At the end of the term when the students (aprox 50 working at the same time) got very
busy the tomcatserver
stoped replying frequently. We have a configuration with
Two Sun Sparc Solaris 7 Servers both tomcat 3.2.1 & 3.2.2 a
hi all!
problem:
database access is managed via a java class that is
instantiated and loaded into each clients session. every
PL/SQL function and/or SQL statement a client needs is
called in a method of this class.
first, a connection is opened, the statement is called,
all resultsets a
14 matches
Mail list logo
