I've fixed axis2.xml in latest svn to reflect it :) thanks Rob
-- dims On 3/14/07, Rasile, Rob <[EMAIL PROTECTED]> wrote:
In axis2.xml this timeout is not actually in seconds (despite the comment there). What happens is that the hashmap containing session contexts is cleaned when a new session is created (which is why you see your destroy method invoked on the first client when a second client calls the service). The cleanup method uses milliseconds to determine whether timeouts have occurred - which is why you need to specify the value in msecs (3000). Doing this resolved similar issues I was having - including the service timing out as expected. -----Original Message----- From: Jochen Zink [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 3:33 AM To: [email protected] Subject: [axis2] Destroing a Session based Webservice Hello, I have a session based Webservice. The ConfigContextTimeoutInterval Parameter in axis2.xml is set to 30 seconds. A client calls the Service and after 30 seconds, the destroy method is not(!) invoked. The destroy method are only invoked, if another client calls the service. Is there any possibility, to destroy the service automatically after the configured time? Or is it possible to destroy the service manually? If yes, how can this work? Thanks a lot! Regards Jochen _______________________________________________________________________ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
