-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shivani,
On 9/14/2010 12:21 PM, shivanic wrote: > We have already increased the max perm gen size - but that is not a > permanent solution. As in, if the count of jsp's in the application which is > already in a few thousands - increases twicefold - again the same problem > would arise. It seems to me that this is just something you'll have to do: if you can't operate within your memory space, you either have to re-size your memory space, or segment your application so you can deploy it in pieces. What happens when you have a JSP compiler that can drop classes from PermGen? Do you just re-compile and re-load classes all the time? It sounds like you'll end up trading PermGen memory space for file I/O. Maybe that's acceptable for you. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyP15MACgkQ9CaO5/Lv0PCJOwCeK0ynMbuvoFAAC39nq88YQhZx bUQAoJOwx0KR/ljQoXprW3gfmk5ra8xM =peIy -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
