Inactive sessions

[Jayaraman Ashok]

Hi
The setup is Oracle 8.1.6.3.0 on Aix 4.3.3 running 11i applications.
The application server is another rs/6000 running Aix 4.3.3 , where
all the forms and reports are installed.
Now the client connections are made either through the browser
directly
(self service modules like HR) and through the forms. The former type
is the JDBC thin client connection.
Now numerous sessions keep running on the database server even after
the client has disconnected. There are many sessions with 'INACTIVE'
status. I have set sqlnet.expire_time=10 in my sqlnet.ora. But i feel
that the resources held by such sessions are not released. How to
tackle this situation? If the client closes his browser or forms
session abnormally, the shadow process on the server side should be
killed.

Cheers,
Ashok

[Howard J. Rogers]

I agree they should be. But have you implemented MTS (which will mean that
you couldn't care?)

Regards
HJR

"Jayaraman Ashok" <ashok_jayaraman@yahoo.com> wrote in message
news:7ca2852.0212232059.5a60b3a1@posting.google.co m...

> Hi
> The setup is Oracle 8.1.6.3.0 on Aix 4.3.3 running 11i applications.
> The application server is another rs/6000 running Aix 4.3.3 , where
> all the forms and reports are installed.
> Now the client connections are made either through the browser
> directly
> (self service modules like HR) and through the forms. The former type
> is the JDBC thin client connection.
> Now numerous sessions keep running on the database server even after
> the client has disconnected. There are many sessions with 'INACTIVE'
> status. I have set sqlnet.expire_time=10 in my sqlnet.ora. But i feel
> that the resources held by such sessions are not released. How to
> tackle this situation? If the client closes his browser or forms
> session abnormally, the shadow process on the server side should be
> killed.
>
> Cheers,
> Ashok

[Frank]

Howard J. Rogers wrote:

> I agree they should be. But have you implemented MTS (which will mean that
> you couldn't care?)
>
> Regards
> HJR
>

<snip!>

Confusion strikes again - do you mean to say MTS is a bad idea
in this case? Not seem many apps installs, but afaik MTS is 'standard'.

Grtz, Frank

[Howard J. Rogers]

"Frank" <fbortel@home.nl> wrote in message news:3E0836A7.4010309@home.nl...

> Howard J. Rogers wrote:

> > I agree they should be. But have you implemented MTS (which will mean

that

> > you couldn't care?)
> >
> > Regards
> > HJR
> >

> <snip!>
>
> Confusion strikes again - do you mean to say MTS is a bad idea
> in this case? Not seem many apps installs, but afaik MTS is 'standard'.
>
> Grtz, Frank
>

Clearly some incomprehension of the English language. MTS means he wouldn't
care about stalled sessions, because the server processes would be off being
busy on behalf of other sessions.

Does that sound like a bad idea to you?

HJR

[Karsten Farrell]

"Jayaraman Ashok" <ashok_jayaraman@yahoo.com> wrote in message
news:7ca2852.0212232059.5a60b3a1@posting.google.co m...

> Hi
> The setup is Oracle 8.1.6.3.0 on Aix 4.3.3 running 11i applications.
> The application server is another rs/6000 running Aix 4.3.3 , where
> all the forms and reports are installed.
> Now the client connections are made either through the browser
> directly
> (self service modules like HR) and through the forms. The former type
> is the JDBC thin client connection.
> Now numerous sessions keep running on the database server even after
> the client has disconnected. There are many sessions with 'INACTIVE'
> status. I have set sqlnet.expire_time=10 in my sqlnet.ora. But i feel
> that the resources held by such sessions are not released. How to
> tackle this situation? If the client closes his browser or forms
> session abnormally, the shadow process on the server side should be
> killed.
>
> Cheers,
> Ashok

This behavior is very common with application servers. They (usually)
maintain a "connection pool" so that the next application can grab any
available member. The pool issues network "keep alive" messages every so
often to maintain the connection, but these don't count as active sessions.
They're active from a network standpoint, which is why they don't time out
(or if they do, the application server immediately re-establishes the
connection to maintain the pool count).

[Frank]

Howard J. Rogers wrote:

> "Frank" <fbortel@home.nl> wrote in message news:3E0836A7.4010309@home.nl...
>

>>Howard J. Rogers wrote:
>>

>>>I agree they should be. But have you implemented MTS (which will mean

>>

> that
>

>>>you couldn't care?)
>>>
>>>Regards
>>>HJR
>>>

>>
>><snip!>
>>
>>Confusion strikes again - do you mean to say MTS is a bad idea
>>in this case? Not seem many apps installs, but afaik MTS is 'standard'.
>>
>>Grtz, Frank
>>

>
>
> Clearly some incomprehension of the English language. MTS means he wouldn't
> care about stalled sessions, because the server processes would be off being
> busy on behalf of other sessions.
>
> Does that sound like a bad idea to you?
>
> HJR
>
>

No - au contraire: an excellent idea; hence the confusion.
miscomprehended the 'you couldn't care less' bit as
'you should have known better than installing MTS' ...

Frank

[Unregistered]

hi how do you resolve the proble?! install MTS? please help me i have the same problem!!! thanks