Saul, watch your thread usage. jBoss will usually throw an out of memory
exception when it can't create a new thread... On Solaris, you have a hard
limit of threads.
I don't know if this is your actual problem, but I thought I would mention
it.
Jim
--On Friday, July 06, 2001 6:47 PM -0400 Saul Farber <[EMAIL PROTECTED]>
wrote:
> Hello again,
>
> I'm having some trouble with Jboss/Jetty running out of memory after
> some heavy use. There's 192M of real memory and another 256M of shared
> memory on a solaris 2.6 install. However, after some heavy use, the jvm
> running Jboss takes up about 85M of real memory, doesn't use swap, and
> then starts spitting java.lang.OutOfMemoryError s.
>
> Any way to tune down Jboss so that any optional/caching features are
> disabled, and therefore less memory is used?
>
> Plus, I thought that java was (mark and sweep) auto-garbage collecting.
> How can I be running out of memory when memory leaks are that much
> harder to come upon?
>
> Thanks!
>
> Saul
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
********************************************
I shall be telling this with a sigh
Somewhere ages and ages hence:
Two roads diverged in a wood, and I -
I took the one less traveled by,
And that has made all the difference.
- Robert Frost, 1916
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
