The GrowableArray is used to implement many of the internal Java virtual
machine functionality (in the native code portions).
In your application, one of the internal GrowableArrays was 65m in size and an
attempt to allocate a 130m block failed. Even if the operation succeeded in
allocating
Leave the gcinterval set as is, or better yet, make it larger. This is the
amount of time (1 hour in this case) the jvm will wait before firing up a full
garbage collection to collect any leftover objects lying around from rmi usage.
Doing this is a useless exercise within an app server but the
One additional answer. Swap space is 2GB.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136875#4136875
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136875
___
jboss-user m
Thanks, Peter. Definitely looks like we're leaking someplace.
Just found out from admins that the startup params are:
-Xms2048m -Xmx2048m -Dsun.rmi.dgc.client.gcInterval=360
-Dsun.rmi.dgc.server.gcInterval=360
There's 8GB on the box and two instances running with these settings. Not
Looks like the JVM is attempting to allocate another 128MB of memory (probably
to expand the heap) and the OS is saying that it can't allocate the memory
because it has run out - even the swap space is full.
How much RAM do you have? What is your swap space size? What is the non-JBossAS
memory
Was a resolution ever found for this problem? Different JVM options?
What are the odds that we would see the exact same error with the exact same
size?
Exception java.lang.OutOfMemoryError: requested 131072000 bytes for GrET* in
/BUILD_AREA/jdk1.5.0_14/hotspot/src/share/vm/utilities/growableAr
Oh, you should also run a profiling tool, such a JProbe, on your application.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023806#4023806
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023806
_
See http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html, especially the
-verbose:gc and -XX:PrintHeapAtGC options.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023805#4023805
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
hi peter,
our application is real time application(core banking application) ,so can't
say how many object are at run time, after few minutes(45m) jboss trimented. .
if you know then tell me how to see run time objects in heap.
if any Monitor tool for jboss??
thanks,
MD
View the original po
According to the error message, the app is allocating a 130MB object. How many
of these huge objects do you have around?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023132#4023132
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
10 matches
Mail list logo
