my 2 bits. when I tried to replicate the issue LeeAnn saw, it was pretty clearn the JVM can't resize the heap fast enough to account for the large number of webapps being loaded. simply increasing the initial heap "should" solve the problem.
peter On 4/21/05, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > From: J. Ryan Earl [mailto:[EMAIL PROTECTED] > > Subject: RE: OutOfMemoryError - 100 thread limit? > > > > So let me get this straight, LeeAnn is specifying a maximum > > heap size of 512MB and a minimum size of 128MB. It looks > > like the heap doesn't get adjusted up when the servlets are > > initializing? Thus she needs to increase her minimum heapsize, > > so something like -Xms512m should fix it? > > Probably not, since I suspect she's running out of perm gen space. > IIRC, the perm gen size is calculated from -Xmx, which is already at > 512m. Using the PrintGCDetails will tell us for sure. If that shows > perm gen space to be exhausted, then adjusting -XX:MaxPermSize should > fix it. > > - Chuck > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail > and its attachments from all computers. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
