In this topic we are going to discuss on how to resolve "java.lang.OutOfMemoryError: Metaspace" error in Oracle Weblogic while start up of a Oracle SOA CS instance. Please follow the step by step process as mentioned below.
Related Questions/Queries :
- Oracle Weblogic SOA 12c Server is not starting due to out of memory.
- Java OutOfMemoryError error in Oracle Weblogic Server.
- Java Metaspace error in Oracle weblogic.
- Oracle SOA 12c Out Of Memory Error.
Description of Use case :
- Oracle Weblogic server is not starting due to "OutOfMemoryError: Metaspace" error.
Error Details :
at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:89)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:250)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:358)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:305)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2126)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:116)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:90)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1237)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1168)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused By: java.lang.OutOfMemoryError: Metaspace
Solution :
1.Take the backup of setDomainEnv.sh file of our Oracle SOA 12c instance.
2. Add below parameters in setDomainEnv.sh.
In setDomainEnv.sh file, find the bellow snippet..
JAVA_OPTIONS="${JAVA_OPTIONS}"
export JAVA_OPTIONS
Change it as :
JAVA_OPTIONS="${JAVA_OPTIONS} -XX:MaxMetaspaceSize=1024m"
export JAVA_OPTIONS
[ try to put some higher size ie. 1024m]
3. Save, restart server after change and monitor server activity.
This way you can resolve the 'Metaspace' error in your Oracle Weblogic SOA 12c instance.
Feel free to post your comments/suggestions/queries. I shall be happy to respond to those.
Thank You . Happy Learning !!
Weblogic Server -java.lang.OutOfMemory:Metaspace in SOA CS
Reviewed by Technophile-SOA-OIC Blog
on
June 30, 2020
Rating:
No comments:
Comment