Funny, I started having a similar problem yesterday. I'm running Axis on WLS 7.1. I'm reasonably sure that my impl doesn't have any stale reference issues as it is pretty basic -- it is just a bridge between .NET and JMS. I'm also using application scope. My web service got pegged pretty good yesterday (250,000 invocations), it started choking with OutOfMemoryError as well. I increased the max heap from 256MB to 512MB and it seems to be doing much better. I haven't profiled it yet, but will be interested to hear what others say. I'm running the nightly build from May 31st.
Mike -----Original Message----- From: ow [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 10:28 AM To: [EMAIL PROTECTED] Subject: Axis/Tomcat memory leak? java version "1.4.1_02" Tomcat 4.1.24 Axis 1.1 Build 0206 June 7 2003 Hi, A deployed WS works fine for 1, 10, ..., 10K invocations. With 100K invocations, Tomcat dies with OutOfMemoryError. I'm pretty sure that it's not a problem with the logic that the WS calls since the logic works for 10M invocations without any problems. The WS was deployed with deployscope="session" and I see about 66K of org.apache.catalina.session.StandardSession objects hanging around. It appears that new session is created for each WS call even though I reuse the same "binding" for all calls. BTW, changing scope to "application" does not help, Tomcat still dies with OutOfMemoryError. Also, there's about 13K instances of java.util.Hashmap which seems somewhat large ... I can increase the Tomcat's heap at startup and then 100K invocations work fine but, obviously, this is not a solution in the long term. Any ideas? Thanks __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com
