您的位置:首页 > 编程语言 > Java开发

使用bsu打补丁时出现 java.lang.OutOfMemory错误解

2016-01-04 11:21 615 查看
使用bsu打补丁时出现 java.lang.OutOfMemory错误解

WebLogic Server: Smart Update Throwing OutOfMemoryError (Doc ID 1154089.1)To
Bottom
In this Document

Symptoms
Cause
Solution


APPLIES TO:

Oracle WebLogic Server - Version 9.2 to 12.1.1.0

Information in this document applies to any platform.

***Checked for relevance on 4-May-2015***


SYMPTOMS

An issue has been reported of the Smart Update utility throwing an OutOfMemoryError when using bsu.cmd or bsu.sh script inside WL_HOME/utils/bsu directory. Below is the exception trace in bsu.log at the time
of the issue.

JVMDUMP013I Processed Dump Event "systhrow", detail "java/lang/OutOfMemoryError". 

Exception in thread "main" java.lang.OutOfMemoryError 

at org.apache.xmlbeans.impl.store.Cur.createElementXobj(Cur.java:257) 

at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.startElement(Cur.java:2992) 

at org.apache.xmlbeans.impl.store.Locale$SaxHandler.startElement(Locale.java:3194) 

at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportStartTag(Piccolo.java:1082) 

at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseOpenTagNS(PiccoloLexer.java:1473) 

at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseTagNS(PiccoloLexer.java:1362) 

at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXMLNS(PiccoloLexer.java:1293) 

at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXML(PiccoloLexer.java:1261) 

at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:4808) 

at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290) 

at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400) 

at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714) 

at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3435) 

at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1270) 

at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1257) 

at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345) 

at com.bea.cie.common.dao.xbean.XBeanDataHandlerSpiImpl.create(XBeanDataHandlerSpiImpl.java:130) 

at com.bea.cie.common.dao.xbean.XBeanDataHandlerSpiImpl.create(XBeanDataHandlerSpiImpl.java:111) 

at com.bea.plateng.patch.dao.cat.PatchCatalogFactory.create(PatchCatalogFactory.java:163) 

at com.bea.plateng.patch.dao.cat.PatchCatalogFactory.create(PatchCatalogFactory.java:85) 

at com.bea.plateng.patch.dao.cat.PatchCatalogFactory.create(PatchCatalogFactory.java:71) 

at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchCatalog(PatchCatalogHelper.java:57) 

at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:363) 

at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130) 

at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201) 

at com.bea.plateng.patch.Patch.main(Patch.java:281)


CAUSE

The issue happens if the default heap size used by the Smart Update java process is insufficient while launching the Smart Update GUI or applying the patches.


SOLUTION

To resolve this issue, increase the heap size for bsu inside the bsu.cmd or bsu.sh script inside WL_HOME/utils/bsu directory. Add Xms and Xmx arguments for increasing the heap size.
For example, set Xms and Xmx values to 512m for the BSU process inside bsu.sh script inside WL_HOME/utils/bsu directory:

#!/bin/sh 

JAVA_HOME="C:/BEA/WLS92.3/jrockit_150_12" 

"$JAVA_HOME/bin/java" -Xms512m -Xmx512m -jar patch-client.jar $*

摘自support.oracle.com
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息