Re: Orphan database connections

Tcp_timedwaitdelay indefinite perhaps?

Something in the TCP stack keeping the socket open on the clients PC

Chris

On Wed, Sep 4, 2019, 10:57 AM Jeffrey Beckstrom <jbeckstrom_at_gcrta.org> wrote:

> We are in the very early stages of a desktop migration to Windows 10. To
> date, only 3 IT personnel that use Oracle have a Windows 10 PC. Of those,
> two are experiencing a problem. If you are in SQL Plus or SQL Developer and
> do not exit/close the connection prior to closing the application's window,
> the database connection remains after the program is terminated. This does
> not occur on any of our Windows 7 desktops. We have not been able to
> identify a difference between the PC that does terminate the database
> connection upon the window being closed and the two that do not. All of our
> PCs start from a standard image.
>
> Oracle is suggesting looking at the network, however, all of the PCs are
> inside the firewall and if in SQL PLus you state "exit" or in SQL Developer
> you right click the connection and choose disconnect, the connections are
> terminated. The issue only arises on 2 out 3 PCs if just close the Window
> without taking any other actions first.
>
> Any suggestions on what may be the cause? Does Windows 10 not send a
> termination message and thus you now have ensure you break the connection
> manually?
>
> Jeffrey Beckstrom
> Lead Database Administrator
> Information Technology Department
> Greater Cleveland Regional Transit Authority
> 1240 W. 6th Street
> Cleveland, Ohio 44113
>
>

--
http://www.freelists.org/webpage/oracle-l