Running While Calling A writeTemplate Gives ClassNotFoundError

(Doc ID 2210907.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


On : version:

1) There are two issues with the writeTemplate: ClassNotFoundError

When running writeTemplate(),  it fails with the error:

Nov 08, 2016 4:22:27 PM handleException
SEVERE: Error: writeTemplate() failed. ConfigHelper: Unable to writeTemplate.


Patch 2254132 resolves this issue.

2)  After applying Patch 2254132, 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] - Exception in writeTemplate:
weblogic.rjvm.PeerGoneException: ; nested exception is:


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.





Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms