AW: JDBC connection leak

2002-03-08 Thread Marc Lehnert
Hi! Problem solved. I removed all the JDBC things and implemented two more finder methods for min and max of date such as: finder-method query=$rw_websiteID = $1 and rw_datetime in (select min (rw_datetime) from logfilerow where $rw_websiteID = $1) method ejb-nameLogFileRow/ejb-name

JDBC connection leak

2002-03-07 Thread Marc Lehnert
Hello! I call the following code in a Message Driven Bean in Orion 1.5.2. After the conn.close() all entity beans I created in some code before are destroyed. The database is empty. The sql statement gets the right result but after the close everything is lost. No error, nothing. Without the

Re: JDBC connection leak

2002-03-07 Thread Stephen Davidson
Hi Marc. Maybe try a conn.commit() before conn.close()? -Steve Marc Lehnert wrote: Hello! I call the following code in a Message Driven Bean in Orion 1.5.2. After the conn.close() all entity beans I created in some code before are destroyed. The database is empty. The sql statement gets

RE: JDBC connection leak

2002-03-07 Thread John Creaner
(); stmt.close (); conn.close(); This means that the connection is now free for the CMT to use again (I THINK ;) john -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marc Lehnert Sent: 07 March 2002 15:56 To: Orion-Interest Subject: JDBC connection leak