We've been consistently having this problem, too, after about 5-6 hours
(~60,000 transactions) of stress testing. We're using JBoss 2.2.1 + Tomcat
3.2.1 on a Linux box with 200 MB of RAM allocated for the JBoss VM. Here's
a specific example of the error message:
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested
53687
0924 bytes
We've been monitoring memory usage, and the JBoss VM was only using about
10% of the available memory at the time of the error, so that's clearly not
the problem.
We'll start monitoring thread usage, as per Jim Archer's comments, but in
the meantime, does anyone have any other insights/suggestions? We'd
actually like to start using JBoss in a production system soon, but this
could be a real problem!
> "JA" == Jim Archer <<EMAIL: PROTECTED>> writes:
>
> JA> Saul, watch your thread usage. jBoss will usually throw an out of
> JA> memory exception when it can't create a new thread... On Solaris,
> JA> you have a hard limit of threads.
>
> JA> I don't know if this is your actual problem, but I thought I would
> JA> mention it.
>
> I think there should be a bug open. We've had a lot of problems with
> this on a Linux box.
>
> --
> Nicolai P Guba http://www.gnu.org http://www.frontwire.com
> mailto:<EMAIL: PROTECTED> mailto:<EMAIL:
PROTECTED>
> GSM: +44 (0)7909 960 751 DDI: +44 (0)20 7368 9708
--------------------------------------------------------------------
Jim Gloor ([EMAIL PROTECTED])
Senior Software Engineer, Open Ratings, Inc.
928 Commonwealth Avenue
Boston, MA 02215-1204
(617) 582-5159
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
