hello
you might have opened the connections in the try{} block and
catched the exceptions in the catch{} block.
now you write finally{} block.
Inside the finally{} write another try-catch block.
Close the connections in the reverse order in the try{} block and catch the
exceptions
in the catch block.
Ketan Puri
B-26, Sector 57,
Noida-201301
Tel: 91-11-91 4581236-41
Fax: 91-11-91 4581235
Email: [EMAIL PROTECTED]
[EMAIL PROTECTED]
> -----Original Message-----
> From: Shyam Sankar S. [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, June 22, 2000 4:12 PM
> To: [EMAIL PROTECTED]
> Subject: Database Connection
>
> Hi all,
>
> We are working on Bean Managed Persistent Entity Beans. We got a mail now
> from our DBA that there are around 200 sessions open in the Oracle Server.
> This could be because our connection.close statements don't work or maybe
> don't get called. Could anyone tell me which is the right place in an
> Entity Bean to:
> 1. Open Connection
> 2. Close Connection
>
> Presently, Connection is opened in the setEntityContext and closed in
> unsetEntityContext. unsetEntityContext is not called explicitly.
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
