Re: oracle threads increasing, even after closing sessions

On Jun 15, 1:14 am, Jimmy <jimmy.coole..._at_gmail.com> wrote:
> On 14 jun, 17:23, yong..._at_yahoo.com wrote:
>
>
>
> > On Jun 14, 11:11 pm, Cristian Cudizio <cristian.cudi..._at_yahoo.it>
> > wrote:
> > ...
>
> > > > By the way, DCD won't work because the SQL*Net connection is left
> > > > intact and TCP connection state is still established.
>
> > > but if there is not a client process (that opened the socket)
> > > responding i can't figure out why it will
> > > not detect a death connection ....
>
> > > > Yong Huang
>
> > > Bye
>
> > > Cristian Cudizio
>
> > >http://oracledb.wordpress.comhttp://cristiancudizio.wordpress.com
>
> > Isn't it true that DCD can only tear down a connection and terminate
> > its server process if the client doesn't respond to an "Are you
> > there?" packet? If the connection is healthy, the software client
> > (sqlplus) does respond with a "Yes, I'm here", although the human
> > client (user) can't type any command, other than exit and connect.
>
> > Yong Huang
>
> When i check for TCP connections on the server,
> i see a lot of TCP connection in the state CLOSE_WAIT; these
> connection are from the Webserver ( hosting the ASP application )

I assume your "server" here is the Oracle server, not the Websphere. How long do these connections stay in CLOSE_WAIT state? What are the corresponding connection states on the Websphere side?

We thought your application did something similar to sqlplus's disconnect, but it doesn't look like, because in that case you would see ESTABLISHED state. I'm not sure if there's some bug in .net connector. You may want to search on Metalink or open a Tar.

Yong Huang Received on Fri Jun 15 2007 - 03:47:33 CDT