axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stadelmann Josef" <>
Subject AW: Lifecycle interface
Date Mon, 07 Feb 2011 17:17:37 GMT
Hi Chris


I am happy that you got it work. 

Keep the timeout definition in axis.xml in mind. And increase the timeout as needed and lower
it as needed. 


And if one on a day, you have the demand (like I have) to have destroy() called before the
timeout triggers, 

well, let's work together because this is my open low priority issue on axis2/J and /C as


And regarding default scope ---- NO ---- default scope is --à please read at link below.


Best Regards



Von: Christopher Johnson [] 
Gesendet: Montag, 7. Februar 2011 14:46
Betreff: Re: Lifecycle interface


Josef -

As it turned out I did not specify the scope in the services.xml to be of scope="soapsession"
 Once I did that everything worked as you described.

What is the default scope, application ?



On Mon, Feb 7, 2011 at 3:55 AM, Stadelmann Josef <>

Is destroy called by the server itself?


Are you talking about a service in scope="soapsession"?


If yes, destroy() gets called when 

a) the service has timed-out (configured in axiom.xml) and 

b) when a next request (not necessarily to the same service or servicegroupId) is received
at the server. 


Our parameter:

<parameter name="ConfigContextTimeoutInterval">28800000</parameter>


In scope="soapsession"

When a request arrives a check is made for timed out services. 

Therefore the destroy method is called only when a request comes in and this housekeeping
finds the timeout condition.

Unfortunately we have no method to force the timeout..

Only in case when timeout-condition for a servicegroupId exists the destroy() is sent to the
service and taken of a list of long lasting services.





Von: Christopher Johnson [] 
Gesendet: Donnerstag, 3. Februar 2011 17:00
Betreff: Lifecycle interface


All -
I have a service in place the returns a set of attachments using SwA.  These attachments are
generated on the server and placed in a tmp directory before they are returned.

I've implemented the Lifecycle interface so I can cleanup the tmp files after the service
returns in the destroy method, although after testing I've noticed that destroy is not called
in my service.  From the look of it init is called for every new session yet once my client
gets its results destroy is not being called..  Any tips on how to resolve this issue ? 

Thanks in advance,


View raw message