Here is what i did to overcome this "problem": After defining my own SessionListener and invalidating the created sessions immediately i got some exceptions thrown by axis. So my current solution is to extend the AxisServlet, overriding the service method and invalidate the session after super.service was called. Works fine in my testing environment.
-- Andreas KI> (tomcat)/conf/web.xml will contains session-timeout settings, KI> and that value is default to 30 min. KI> (tomcat)/webapps/axis2/WEB-INF/web.xml will not have this settings. KI> I'm not sure but here is my guess, KI> Service will run as servlet of tomcat, I think. KI> And each servlet threads for invoked services will remain as session. KI> After receiving request and send back response, KI> web service session should be clear or invalidate by Axis2. KI> But results of your test seems to remain those sessions until timeout. KI> So, set the session-timeout to minimum value is work around for this. KI> How everyone think about this ? KI> Regards, KI> kinichiro KI> __________________________________________________ KI> Do You Yahoo!? KI> Tired of spam? Yahoo! Mail has the best spam protection around KI> http://mail.yahoo.com KI> --------------------------------------------------------------------- KI> To unsubscribe, e-mail: [EMAIL PROTECTED] KI> For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
