Title: RE: Urgent: How to know when a Session has been terminated within Apache SOAP

Thanks Scott,
        Then, there is absolutely no way to free session allocated resources in Apache SOAP?
        I thought that, for example, releasing a backend database connection when the session-enabled client connection drops would be a very common problem.

        How do people get around this issue?
      Do they have to implement some sort of inactivity timers on the backend connections/allocated resources?

Thanks!
Joan.


-----Original Message-----
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: 28 November 2003 19:07
To: [EMAIL PROTECTED]
Subject: Re: Urgent: How to know when a Session has been terminated within Apache SOAP

You are not notified from within SOAP code when a session ends.

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message -----
From: "Joan Pont" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 28, 2003 12:06 PM
Subject: Urgent: How to know when a Session has been terminated within Apache SOAP


> Hi,
> I would really appreciate any help/suggestions regarding this issue.
> I have a problem regarding allocation/reallocation of resources per
> session.
> The idea is that some resources are allocated to be able to service
> a session enabled client when we receive the first request. Those resources
> must be deallocated when the session terminates.
>        I need to know/be notified when the HTTP session has been terminated
> within the SOAP code.
> Does SOAP know when the HTTP session has been terminated?
> For example the client connection has dropped and effectively the
> Tomcat knows that this session is not active anymore. Can I get notified of
> that event within Apache SOAP?
> Is there way so I can free session allocated resources when a
> session terminates?
> Is there for example a session listener interface that can be
> implemented?
>
> Many thanks,
> Joan.
>
>

Reply via email to