Hello all,
I also encountered the memory leak problem in SoapService. Ben's patch looks OK.
But I have a question, why is there this hashtable ? sessions is
private, and there is not method/accessor to read its content, we only
can add new Session.
This hashtable was added in version 256500. And
oops! Please submit a bug report with the patch :)
thanks,
dims
On 11/21/05, Ben Gunter <[EMAIL PROTECTED]> wrote:
> Hello all. I'm running Axis 1.3 under Tomcat 5.5.12 on Windows XP and
> on Solaris 9. I have deployed a session-scoped service using the
> SimpleSessionHandler. I discovered the
i'd recommend using HTTP sessions because the soap header based
session tracking is non-standard.
thanks,
dims
On 11/21/05, Ben Gunter <[EMAIL PROTECTED]> wrote:
> Hello all. I'm running Axis 1.3 under Tomcat 5.5.12 on Windows XP and
> on Solaris 9. I have deployed a session-scoped service usi
