Running wlst.sh While Calling A writeTemplate Gives ClassNotFoundError
(Doc ID 2210907.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle WebLogic Server - Version 12.2.1.0.0 to 12.2.1.0.0 [Release 12c]Information in this document applies to any platform.
Symptoms
On : 12.2.1.0.0 version:
1) There are two issues with the writeTemplate:
wlst.sh ClassNotFoundError
When running writeTemplate(), it fails with the error:
Nov 08, 2016 4:22:27 PM com.oracle.cie.domain.script.jython.CommandExceptionHandler handleException
SEVERE: Error: writeTemplate() failed.
com.oracle.cie.domain.script.jython.WLSTException: javax.management.MBeanException: ConfigHelper: Unable to writeTemplate.
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:2360)
at com.oracle.cie.domain.script.jython.WLScriptContext.writeTemplate(WLScriptContext.java:3392)
<Patch:22541322> resolves this issue. See also <Note:2360005.1> WriteTemplate Failed On Remote Host
2) After applying Patch 22541322, the writeTemplate is working but is causing the memory in Weblogic to run out. This is then shutting down Weblogic:
2016-11-15 15:32:46,725 WARNING [1] com.oracle.cie.domain.script.ScriptExecutor - Exception in writeTemplate:
weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
JVM memory leak found during online writeTemplate. The issue manifests itself as a JVM native memory leak when running writeTemplate() against a domain whose packed template size would be greater than 10M.
Because JDK8 removed perm gen, classloader/class leak means native memory leak.
This is documented in the Unpublished Bug 23472886 - JVM NATIVE MEMORY LEAK IN ADMIN SERVER ON LOOP RUN TO CREATE AND REMOVE MS.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |