目前的内存占用情况是:
[weblogic@db-gwyx-3 shortcut]$ free -m
total used free shared buffers cached
Mem: 14053 13855 198 0 50 453
-/+ buffers/cache: 13351 702
Swap: 8191 6249 1942
但是启动WebLogic应用报错:
部分错误信息:
-------
r.log is opened. All server side log events will be written to this file.>
Exception in thread "VDE Transaction Processor Thread" java.lang.OutOfMemoryError: Java heap space
at com.octetstring.vde.Entry.readBytes(Entry.java:506)
at com.octetstring.vde.Entry.<init>(Entry.java:98)
at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:234)
---------------
AutoloadOackage:singlesignon
ASYNTASK_SERVER_AUTO_START:null
<Aug 25, 2014 8:33:05 PM CST> <Error> <HTTP> <BEA-101216> <Servlet: "action" failed to preload on startup in Web application: "web".
javax.servlet.UnavailableException: Parsing error processing resource path
/WEB-INF/billing/struts-config-calc.xml,
/WEB-INF/billing/struts-config-price.xml,
/WEB-INF/billing/struts-config-report.xml,
/WEB-INF/mr/struts-config-read.xml,
/WEB-INF/credit/struts-config-credit.xml,
/WEB-INF/sc/struts-config-contract.xml
at org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1038)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1017)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
Truncated. see log file for complete stacktrace
>
1 个解决方案
#1
it looks like u really have a memory issue on the server. There is no too much file system buffer and block device cache at all. You may consider to play the memory allocation of your JVM a bit. If it still doesn't work, I am afraid you will have to offer more physical RAM.
the parameters of JVM you may pay attention:
-Xmx
-Xms
-XX:MaxPermSize
tweak these parameters a bit will help a lot. ur question is a FAQ for all j2ee containers...
the parameters of JVM you may pay attention:
-Xmx
-Xms
-XX:MaxPermSize
tweak these parameters a bit will help a lot. ur question is a FAQ for all j2ee containers...
#1
it looks like u really have a memory issue on the server. There is no too much file system buffer and block device cache at all. You may consider to play the memory allocation of your JVM a bit. If it still doesn't work, I am afraid you will have to offer more physical RAM.
the parameters of JVM you may pay attention:
-Xmx
-Xms
-XX:MaxPermSize
tweak these parameters a bit will help a lot. ur question is a FAQ for all j2ee containers...
the parameters of JVM you may pay attention:
-Xmx
-Xms
-XX:MaxPermSize
tweak these parameters a bit will help a lot. ur question is a FAQ for all j2ee containers...