Deployment issues Archive

Deployment Issues On Weblogic Server

When we deploy web applications on the weblogic server, there are some common errors seen on the admin console while activating changes. These errors are usually not resolved even after restart of the server. Few of the issues are as below:

1) <Error> <Console> <BEA-240003> <Console encountered the following error [Deployer:149189]Attempt to operate ‘distribute’ on null BasicDeploymentMBean for deployment portalTramitsServeisEAR. Operation can not be performed until server is restarted.

– This may be resolved by running statd() and lockd() processes on every NFS client that accesses a remote NFS volume.

– If different servers (sharing the same domain root) are started with different user Ids of same group, set the correct “umask” for the server process so that the file created by one server can be opened for read/write by the other server without security exceptions. Eg: “umask 002”.

Workaround for this issue:
1.  Click on Lock and Edit.
2.  Go to deployments.
3.  Click to install the web-app.
4.  After installing (any staging mode), click on Activate changes. At this time, you will see the error as mentioned above.
5.  Now click on Activate Changes again.
6.  Click on Lock and Edit.
7.  Click on Undo All Changes.
8.  Click on Lock and Edit and install the app again.
9.  This time it succeeds.

2)  javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(

– When the application is already deployed on the server, any change made through the console throws this error. Suppose the application is deployed on the managed servers, when the servers are running and the application is active, the changes cannot be activated. The workaround for this is to shutdown the managed servers and make any changes. But this is not acceptable in the production environment.

Solution :
1- Undeploy the application. Shutdown the servers.

2- Add xercesImpl.jar, xalan.jar, serializer.jar, xml-apis.jar and xsltc.jar libraries in classpath.

3- In the application, place the file xalan.jar, xercesImpl.jar and xml-apis.jar in the war file i.e web-inf/lib directory, then set prefer-web-inf-classes to true in weblogic.xml as:

4- Set the following start-up flags in the JAVA_OPTIONS:
– Restart the servers, deploy the application again, and check if the issue still persists.


<BEA-290071> <Deployment service servlet failed on parsing the request or uploading the file>

Use the following java option


Unable to access the selected application.
Exception in AppMerge flows’ progression
Exception in AppMerge flows’ progression
VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a:

You need to update your web.xml namespace declaration.

You get the following exception when jsp size is huge.

too large for try statement

Use the following JVM Option


Getting following error at the time of deployment.

Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger

Apply Patch 16038283 and excluding classes which are not used as beans by editing the beans.xml file.
If the issue is still not resolve please get in touch with Oracle Support.

Add the following JVM option on the server on which you are doing the deployment and restart.


Stack overflow error while invoking jspx page WLS 10.3.6

java.lang.StackOverflowError exception occurs .
The related Java Stack is :
at weblogic.servlet.internal.ServletResponseImpl.addHeader(
at javax.servlet.http.HttpServletResponseWrapper.addHeader(

You need to modify the web.xml as below.

javax.faces.FACELETS_VIEW_MAPPINGS *.jspx

Exception in thread “AWT-EventQueue-0” sun.awt.X11.XException: Cannot write XdndAware property
at sun.awt.X11.XDnDDropTargetProtocol.registerDropTarget(

This is due to a JDK bug, add the following jvm option in


java.lang.NullPointerException at com.bea.console.actions.jms.message.JMSMessageDetailAction.execute(JMSMessageD

This issue has been addressed in defect 9889164.

weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
The type new Comparator(){} must implement the inherited abstract method Comparator.thenComparing(Function, Comparator)

Issue is present on WLS 12.1.3 and JDK 8.
You will need to download the patch for bug Bug 18729264.