I did some additional tests here are the results
1) if you connect as sysdba you get only 1 thread
2) I launched a Java program which opens 100 db concurrent
connections and keeps them open for 20 minutes. For all the duration
of the test the thread number was 227, when the program ended the the
number drop to 27
So at least to me the results seem consistents. In the afternoon I
will try to exit from the program without closing the connection in
oder to see if there is some recovery mechanism.
Giovanni
On 2/24/06, Niall Litchfield <niall.litchfield_at_gmail.com> wrote:
> Are your results consistent?
>
> I also appeared to get the same behaviour using XE (which is 10.2 based),
> but not 10.1 or 9.2. However when I reran I discovered that Oracle appeared
> to be more proactive in managing threads on 10.2 than it was in earlier
> versions and that I didn't apparently always get two threads per foreground
> session. I didn't have sqlnet.expire_time enabled. So right now I'm just
> confused as usual.
>
> Niall
>
>
> On 2/24/06, Giovanni Cuccu <giovanni.cuccu_at_gmail.com> wrote:
> >
> > Hi Paolo,
> > I can confirm the issue on 10.2, I also checked the RAM allocated
> > for a single sqplus and it's 3MB, my next question is if the
> > additional thread is given the 1mb stack.
> > Giovanni
> >
> >
> >
> > --
> >
> --------------------------------------------------------------------
> > Another free oracle resource profiler
> > http://sourceforge.net/projects/oraresprof/
> > Now version 0.9
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
> >
>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
--
--------------------------------------------------------------------
Another free oracle resource profiler
http://sourceforge.net/projects/oraresprof/
Now version 0.9
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Feb 24 2006 - 06:09:53 CST
