Um, I take back what I said about the heap.  I was thinking of permgen
memory.

We could use less heap possibly by using resources more economically.
We could analyze this with a Java profiler.  But the best choice at
this point would just be to have more RAM to work with.

-t


On Aug 24, 10:25 am, Turadg <[EMAIL PROTECTED]> wrote:
> The heap size is a setting to launch the *Java* VM.  The VM server
> will be a virtual Intel machine.  (you might call it an x86 VM).
>
> So this doesn't implicate the server VM to have allocated.  It just
> means that when you set up Java on this machine, you give it the right
> command line option.
>
> There's practically nothing we could do differently do require less
> heap.
>
> -t
>
> On Aug 23, 6:10 pm, Jim Slotta <[EMAIL PROTECTED]> wrote:
>
> > I guess the Max heap size is something that is set?  Or is this fixed
> > by the allocated machine?
>
> > Will this situation help us pin down our specs for the new VM server
> > (I'd like to request this tomorrow, if possible...)
>
> > but if we only have 64M max heap size currently and we're bumping up
> > against it, this seems a problem.
>
> > Should we request 640 M?  Or is it the problem that were fully
> > loading the jar files into heap which we shouldn't be doing?
>
> > jds
>
> > > The thing that fixed it was doing a reload of the jnlp servlet through
> > > the tomcat management application.  I'd guess that the problem has
> > > to do
> > > with that tomcat running out of memory.  If it fully loads the jar
> > > files
> > > into memory, it would require 13MB of memory.
>
> > > Looking at the status page after reloading the jnlp servlet shows
> > > this:
> > > Free memory: 8.16 MB Total memory: 63.56 MB Max memory: 63.56 MB
>
> > > Does any one know what that really means?
> > > Does that mean the max heap size of the jvm which tomcat is running in
> > > is only set to 64MB?
>
> > > Scott
>
> > > Scott Cytacki wrote:
> > > > Ok,
>
> > > > Thanks, I can duplicate the problem now.  So now you can go ahead
> > > and
> > > > clear your cache.
>
> > > > Or you might be able to get it to work just by deleting this folder:
>
> > > > /V1.3.1-20070729.130451-662/DMjnlp/DMorg/DMconcord/DMmodeler/
> > > DMworkbench/
>
> > > > (that way you won't have to download all the files again)
>
> > > > Scott


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to