Hi,
AFAIK, Axis 1 did not create HTTP sessions. I believe Axis 2 does, and
that may be the difference.
The suggestion of Andreas may work for you now, but I guess it may lead
you to some problems in a future, as other services or modules may need
the session to store configurations. Anyway, I would prefer a filter for
invalidating the session. Is less "invasive" than an AxisServlet subclass.
I think a better approach would be to "activate" HTTP session support on
your client, if you have control on it. This way, only one session would
be needed on your server. I don't know if this is possible, but being
Axis 2 HTTP transport based on commons-http-client, there must be a way
to activate this.
If the session support is already activated, perhaps you need to
refactor your test somehow to take advantage of it.
Maybe someone can bring some light on this subject :-)
Regards,
Rodrigo Ruiz
Ramanathan, Subramanyam wrote:
Hi,
Regarding setting the session-timeout, I found that session-timeout in Axis1 was set to 5 minutes by default, so I set it to 30 minutes in axis1 as well, just to compare. However, I don't find any big memory consumption increase when I pump requests.
As a matter of fact, the memory usage stays between 10 and 25 M, whereas with
axis2, even after setting session-timeout to 2 min, usage touches 100M
frequently. So I am not sure that setting the session-timeout is a good
workaround.
Is there any reason for this high memory usage in axis2 as against axis1 ?
I have not yet tried Andreas' suggestion, though, and I will do so now.
Thanks and Regards,
Subramanyam
-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 11:43 PM
To: [email protected]; Andreas Hörnicke
Subject: Re: Re[2]: Axis2 High memory usage, OutOfMemory exception
Andreas,
Could you *please* add this info to bug report AXIS2-766?
thanks,
dims
On 5/25/06, Andreas Hörnicke <[EMAIL PROTECTED]> wrote:
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]
--
-------------------------------------------------------------------
GRIDSYSTEMS Rodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorca mailto:[EMAIL PROTECTED]
Baleares - España Tel:+34-971435085 Fax:+34-971435082
http://www.gridsystems.com
-------------------------------------------------------------------
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date: 25/05/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
