Symptoms


Failure to remotely deploy a very large enterprise application using WLST or the Admin console and getting out of memory error while loading the ear file.
WLSTException: 'Error occured while performing deploy : Target exception thrown while deploying application: Error occured while performing deploy :
Deployment Failed. Error occurred while performing deploy : Deployment Failed.

Use dumpStack() to view the full stacktrace.
The load of a remotely located ear file also fails via the Administration console with the following message:

An unexpected exception has occurred processing your request Message:
  Stack Trace: java.lang.NullPointerException
  at com.bea.console.actions.app.install.Flow.uploadApp(Flow.java:256)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Cause


The issue was addressed in bug 9456759. As part of the fix, a system property flag weblogic.deploy.UploadLargeFile was added. In WLS 10.3.4 and higher, this flag should be added to the Java startup options for the deployment client if large files are to be deployed. For earlier versions, apply the patch below: no flag is needed.


Solution


Patches are available for Bug 9456759:
PATCH INFORMATION
WLS VersionPatch Number
9.2.2Patch 9456759
9.2.3Patch 9456759
10.0.1Patch 9456759
10.0.2Patch 9456759
10.3.0Patch 9456759
10.3.1Patch 9456759
10.3.2Patch 9456759

Fixed in: 9.2.4, 10.3.4
To apply one of these patches, click on the link for your WLS version and download the appropriate patch from My Oracle Support. You can also search in My Oracle Support for the patch number for your WLS version:


NOTE: Patches are applied per WLS installation and not per domain. That is, if you apply this patch on one WLS installation, then all of the servers from all the domains in that installation will have this patch. On the other hand, if you have a managed server in another machine in a domain (that is, set up with its own WLS installation), you need to install this patch on that other machine as well. Generally, patches can only be applied while the server is not running because WLS locks the needed files while it is running. If, however, you are able to apply a patch while WLS is running, you must restart WLS before the patch will take effect.

0 Comments