Re: request object & system memory (again)

[Maurice Coyle - Sun ireland - Software Products and Platforms - Internationalization Engineer]

ok, so how much is too much?  i realise it will depend on the amount of users,
so i have probably just answered my own question.  if so, can someone tell me
how to work out the amount of info contained in the session variable at any
given time, if this is possible?

all replies greatly apprecited,
maurice




> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> Importance: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
> Date: Wed, 6 Sep 2000 15:45:26 -0700
> From: Kevin Duffey <[EMAIL PROTECTED]>
> Subject: Re: request object & system  memory (again)
> To: [EMAIL PROTECTED]
>
> No..the request object uses memory only during its scope, a single request.
> Once the response goes back, the thread is freed up as well as any data
> (objects) created during that request. HOWEVER, there is one instance as far
> as I know..that can keep objects around after a request. The only thing that
> I know of is if you put an object in the request that has another reference
> to that same object in a longer scope. For example, if you store an object
> in the HttpSession or ServletContext, and put that same object in the
> request (say before forwarding to a JSP page or something), it will reside
> in memory until ALL references to the object are nulled out. In this case,
> if you have an object that has a reference to it stored in the HttpSession
> (or ServletContext) AND you have a reference to that object stored in the
> request object, then the actual memory will stay in use until the
> httpsession expires or you remove the object from the httpsession (or
> ServletContext). The GC won't do its thing until it can, so even though Java
> handles memory for you, you still have to do your part in making sure all
> references to an object in memory are nulled out.
>
>
> > -----Original Message-----
> > From: Jim Huffsmith [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, September 06, 2000 1:34 PM
> > To: [EMAIL PROTECTED]
> > Subject: request object & system memory (again)
> >
> >
> > (I posted this question yesterday, but our ISP went down
> > right afterwards.
> > As a result, I was cut off from the list and didn't see any of the
> > responses. Can we try it again?)
> >
> > I've heard that you should be careful not to overload the
> > session object
> > with data because it can have a big impact on memory
> > requirements. Is this
> > an issue with the request object as well? Or does the request object's
> > shorter lifetime make it a non-issue?
> >
> >
> > Jim Huffsmith
> > Dove Solutions
> > 641-469-5877 x103
> >
> > ==============================================================
> > =============
> > To unsubscribe: mailto [EMAIL PROTECTED] with body:
> > "signoff JSP-INTEREST".
> > Some relevant FAQs on JSP/Servlets can be found at:
> >
> >  http://java.sun.com/products/jsp/faq.html
> >  http://www.esperanto.org.nz/jsp/jspfaq.html
> >  http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> >  http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
> >
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
>  http://java.sun.com/products/jsp/faq.html
>  http://www.esperanto.org.nz/jsp/jspfaq.html
>  http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
>  http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:

 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html
 http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
 http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets