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. Josef Von: Christopher Johnson [mailto:johns...@gmail.com] Gesendet: Donnerstag, 3. Februar 2011 17:00 An: java-user@axis.apache.org 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, ..Chris
