Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 56791 invoked from network); 1 Apr 2008 09:12:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Apr 2008 09:12:15 -0000 Received: (qmail 29210 invoked by uid 500); 1 Apr 2008 09:12:07 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 29080 invoked by uid 500); 1 Apr 2008 09:12:07 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 29067 invoked by uid 99); 1 Apr 2008 09:12:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 02:12:07 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [62.23.212.5] (HELO smail6.alcatel.fr) (62.23.212.5) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 09:11:14 +0000 Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com [155.132.6.74]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m3195mSH019266 for ; Tue, 1 Apr 2008 11:05:48 +0200 Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 1 Apr 2008 11:11:35 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C893D8.622C27C9" Subject: SOAP-Session management; terminate session. Date: Tue, 1 Apr 2008 11:11:34 +0200 Message-ID: <00275A5B436CA441900CB10936742A3857E423@FRVELSMBS22.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SOAP-Session management; terminate session. Thread-Index: AciT2GIQEFB8mVd7SA2syewojRCibg== From: "LIE Jorund" To: X-OriginalArrivalTime: 01 Apr 2008 09:11:35.0060 (UTC) FILETIME=[623F6540:01C893D8] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C893D8.622C27C9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I would need to use the SOAP session management facilities in Axis2-1.3, = and I have a question about terminating a session. =20 Following the description for session management I have prepared a small = prototype web service that initiates the session, returns the service = group ID for the session to the client, and receives subsequent requests = using the session ID. If there are no requests for a session-ID during a = context timeout interval (set to 30 sec) the session becomes inactive. = So far so good, this works fine, but I have 2 questions tough. =20 1. From tracing the destroy() method of my web service class I see that = the object instance is not destroyed immediately after the context = timeout. It seems like the session becomes stale, and that the object = instance corresponding to stale sessions are destroyed after any new = request to the web service. Is this correct? =20 2. I would like to find a way to terminate the sessions triggered by a = certain operation (e.g. by a logout), not by the inactivity timeout. How = can this be achieved in a clean way? =20 Thanks and Regards. J=F8rund Lie ------_=_NextPart_001_01C893D8.622C27C9 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I=20 would need to use the SOAP session management facilities in = Axis2-1.3, and=20 I have a question about terminating a session.

Following=20 the description for session management I = have prepared a=20 small prototype web service that initiates the session, returns the = service=20 group ID for the session to the client, and receives subsequent requests = using=20 the session ID. If there are no requests for a session-ID during a = context=20 timeout interval (set to 30 sec) the session becomes inactive. So far so = good,=20 this works fine, but I have 2 questions tough.

1. From=20 tracing the destroy() method of my web service class I see that the = object=20 instance is not destroyed immediately after the context timeout. It = seems=20 like the session becomes stale, and that the object instance = corresponding to=20 stale sessions are destroyed after any new request to the web = service.=20 Is this correct?

2. I would=20 like to find a way to terminate the sessions triggered by a certain = operation=20 (e.g. by a logout), not by the inactivity = timeout. How can=20 this be achieved in a clean way?

Thanks and=20 Regards.

J=F8rund=20 Lie

------_=_NextPart_001_01C893D8.622C27C9--