此内容已被标记为最终。 显示 6 条回复
What are your startup arguments (especially -Xmx and -Xms). What JVM are you using?
In most configuration the Admin Server does not have any deployments and requires less heap space. But there are cases where the Admin Server itself is used for hosting applications. Hence first bump your xms and xmx values to 1024MB and then test.
Thanks for the reply.
I see the below startup param
-Xms2800m -Xmx2800m -XX:MaxPermSize=512m
-Xms2048m -Xmx2048m -XX:CompileThreshold=
Java Vesrion is : 1.5.0_06
Thanks in advance.
You have two conflicting sizes, but either way it looks reasonable. Do you have any apps deployed to the admin server?
I'd also suggest adding these startup arguments:
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/some/path/gc.log
replacing /some/path to an appropriate place of course. That way you'll get some indication of what the heap is actually doing.
Mike, yes we have an app on WL. Will try out the option you mentioned and post back.
I am getting the same, althought not consistent. it sort of comes and goes.
Anyway, any resolution?
My memory setting are both 1500M - running on W2008-64bits server.
Exception in thread "VDE Transaction Processor Thread" java.lang.OutOfMemoryError: Java heap space
Edited by: user12307508 on Dec 3, 2009 7:51 PM