Get a copy of OptimizeIt (http://www.optimizeit.com) or JProbe
(http://www.klgroup.com) to find memory problems. I can vouch for
OptimizeIt -- it works very well at finding why objects are still being
referenced after you think they should be gone. Caching, sessions,
and adding objects as event listeners are some common ways that
references
stay around longer than expected.
HTH,
Rod McChesney, Korobra
> Dustin Aleksiuk wrote:
>
> I'm having a small problem and I'm wondering if anyone could give me
> some advice. I'm somewhat new to java and jsp, coming from a C++
> background.
>
> We have a fairly involved e-commerce operation which we are
> implementing in JSP. After about a day or so of fairly good testing
> we start getting an 'out of memory' error.
> We're developing on NT, but our servers run on Solaris. Our test
> server is the basic little Java server that comes with the JSWDK that
> you get from Sun.
>
> Questions:
>
> Has anyone experienced this? Could it be the Web Server we're using
> for our testing (meaning the problem will go away when we move to a
> better web server)?
>
> Also: where should I start looking for this, if the bug is in my code?
>
> Has anyone done any extensive testing on the Jswdk server (or whatever
> it's called) for an extended period of time?
>
> Thanks a lot,
>
> Dustin Aleksiuk
>
> [EMAIL PROTECTED]
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
