> -----Original Message-----
> From: Kumar, Anil [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, July 22, 2000 11:37 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: too many concurrent requests
>
>
> Hi,
> This same problem about out of memory faced by us also. We have
> incrase the
> memory by setting the parameter -mx & -ms. But then also some time its
> gives JVM out of memory.
Which probably means the problem is something else, but it totally depends on
your app and your user load.
> I have a one question on it.????.
> 1. Is there any way to find out that at particular time how much memory is
> free with JVM.
Runtime.getRuntime().freeMemory()
> 2. How much expensive to call gc explicitly.
No expense? No guarantee either.
> 3. Is there any way to to find out frequency of gc.
Enable -verbose:gc. Real handy if you have JRun 3.0 on a UNIX system is that
you can do "./bin/jrun -console -start default" and have JRun started in the
foreground. If you have set java.args to include -verbose:gc, you'll see
messages printed out to the console every time the garbage collector runs.
Then there are commercial tools, such as OptimizeIt and JProbe, pretty much
worth their weight in gold.
Scott Stirling
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
