Re: Question about Connection Pooling...
- From: "Nuno Souto" <dbvision@xxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 21 Mar 2004 00:26:39 +1100
Sorry to push in to this one. Quick related question if
anyone knows:
With this trend to pooled connections/sessions, there is
sometimes a need to make a given session behave with a specific
user's "hat". Does anyone have any scalability info on things
like SET ROLE or any recommendations on how to handle specific
user identification issues? There was something about this a
while ago on the Oracle mag but it was mostly to do with LDAP
authentication and it was for 8i.
Cheers
Nuno Souto
in sunny Sydney, Australia
dbvision@xxxxxxxxxxxxxxx
----- Original Message -----
From: "Gudmundur Josepsson" <gbj@xxxxxxxx>
To: <oracle-l@xxxxxxxxxxxxx>
Sent: Saturday, March 20, 2004 9:28 PM
Subject: Re: Question about Connection Pooling...
> Tanel,
>
> Thanks for the explanation about the difference between connection pooling
> and session pooling. We always talk about connection pooling but
according
> to your definition we're using session pooling. The sessions are opened
> when the app server starts and are kept open continuously. The apps then
> come in on the first free session and might re-appear in a different
session
> on their next call. Makes it a bit tough when it comes to 10046 tracing,
> for example.
>
> Gummi
>
> ----- Original Message -----
> From: "Tanel Poder" <tanel.poder.003@xxxxxxx>
> To: <oracle-l@xxxxxxxxxxxxx>
> Sent: Saturday, March 20, 2004 4:13 AM
> Subject: Re: Question about Connection Pooling...
>
>
> > There is a difference between connection pooling and session pooling in
> Oracle. You might have a pre-allocated pool of connections, but every app
> server request to database still creates a new session using one of the
> connections in connection pool.
> >
> > If you want even better scalability, go with session pooling (done
either
> by app server code or OCI), but if you got need for stateful sessions,
then
> you can't use PL/SQL package variables for saving the states of a session,
> global application contexts and client_id should be used instead.
> >
> > OCI supports both connection and session pooling, I don't know about
IIS.
> >
> > Tanel.
> >
> > > We are using Microsoft IIS for our middle tier. I
> > > did some tests by using a logon trigger and recording the Sid. I
> > > found that
> > > every query results in a new connection. Our software engineers tell
> > > me that the
> > > middle tier is reusing the same connections. I'm not seeing that.
> > > What are your
> > > experiences with connection pooling?
> > >
> > >
> > >
> >
>
> ----------------------------------------------------------------
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> ----------------------------------------------------------------
> To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
> put 'unsubscribe' in the subject line.
> --
> Archives are at //www.freelists.org/archives/oracle-l/
> FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
> -----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
