Re: JDBC connection pool and logon triggers

From: Michael McMullen <ganstadba_at_hotmail.com>
Date: Fri, 28 May 2004 12:17:15 -0400
Message-ID: <BAY9-DAV15jJ3mQy0G8000538b1@hotmail.com>

No rocks thrown here. I always notice exacly the opposite of the original post. I have various audits set up on our users. The jdbc session pools only audit on the very first time the session pool gets activated and after that when the first time a procedure is executed. The rest of the time I don't get any auditing, even though our procedure might be accessed 1000 times/hr.

Mike
ganstadba_at_hotmail.com
----- Original Message -----
From: "Michael Thomas" <mhthomas_at_yahoo.com> To: <oracle-l_at_freelists.org>
Sent: Friday, May 28, 2004 12:09 PM
Subject: RE: JDBC connection pool and logon triggers

> Dan,
>
> Maybe I'm ignorant, since I don't have the time to
> test right now, but that does *not* sound right to me.
> And, I do not remember seeing this so my ignorance
> proves my hypothesis. Sort of like two wrongs make a
> right. ;-)
>
> The "SERIAL#" field in v$session is intended to
> uniquely distinguish a SID, e.g. in case the
> connection is *closed* and the SID value re-used.
>
> My Blasphemy Caused by Hypothetical Results (BCHR):
> Therefore, based on Oracle's implementation of JDBC2.0
> your "connection pool" session should not actually
> close and the "SERIAL#" should not change.
>
> Maybe your Java developers are actually closing the
> connections before handing off to the next process.
>
> Okay, now throw the rocks (since I didn't test it).
> :-)
>
> Regards,
>
> Mike Thomas
>

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Fri May 28 2004 - 11:17:45 CDT