| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.server -> Re: Inactive Dangling Connections When App Crashes.
We used this parameter a year ago with OPS 7.3.3.5 and SQL*Net V2.3.3. Sometimes
we found that sessions were killed that were inactive but nevertheless alive and
reachable by the ping command.
Martin Haltmayer
Andrew Protasov schrieb:
>
> Hi,
>
> Try to set this parameter in server side sqlnet.ora:
>
> SQLNET.EXPIRE_TIME
>
> Purpose:
> Determines time interval to send a probe to verify the session is alive.
>
> Default Value:
> NONE
>
> Minimum Value:
> 0 minutes
>
> Recommended Value:
> 10 minutes
>
> Example:
> sqlnet.expire_time=10
>
> Andrew Protasov
>
> In article <7aj1n8$u8s$1_at_nnrp1.dejanews.com>,
> tim.mcconechy_at_runtime.dk wrote:
> > How does one handle this senerio.
> > The client server app crashes leaving an INACTIVE CONNECTION.
> > TO Oracle.
> >
> > This only happens when the app GPF's or I kill it from the task bar.
> >
> > It doesn't happen much but it happens.
> >
> > Without the obvious (prevent it)
> > Is there ways to handle this????
> >
> > -----------== Posted via Deja News, The Discussion Network ==----------
> > http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
> >
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Wed Feb 24 1999 - 06:40:13 CST
![]() |
![]() |