if you haven't already gotten to the bottom of your problem, one thing
you might try is using DBMS_APPLICATION_INFO.SET_CLIENT_INFO to 'mark'
your connection. in your java app, whenever you open a conn, use this
stored proc with a parameter of something like 'jdbc conn #x'. then
you can look in the CLIENT_INFO column of V$SESSION on the db server
side and see if it matches up the way you think it should.
Joseph Weinstein <bigdog_at_bea.com> wrote in message news:<3F931BB4.5A0EE05E_at_bea.com>...
> Thank you very much for the corroboration.
> Joe
>
> Billy Verreynne wrote:
>
> > Joseph Weinstein <bigdog_at_bea.com> wrote in
> >
> > > He claims that in spite of our debug code which shows whenever
> > > we open an close a connection, (we usually have 20 or so open
> > > at any time), they see the V$Sessions having more
> > > entries than our application claims to have open....
> >
> > And he is likely speaking the truth Joe - from first hand experience.
> >
> > I have seen numerous times that an explicit close JDBC connection in
> > JSP does *NOT* close the session on the Oracle side (see my other
> > posting under this thread).
> >
> > The sessions are only closed when the Java servlet engine is bounced
> > (which is of course done by restarting Apache).
> >
> > --
> > Billy
Received on Wed Oct 22 2003 - 12:43:35 CDT
