weblogic.Deployer Command Waits Forever if Deploy Fails on Managed Server (Doc ID 1134176.1)

Last updated on JUNE 07, 2022

Applies to:

Symptoms

Customer is using the weblogic.Deployer command to deploy an application. They do not have the JDBC connection defined for this application. The scenario is to check when the weblogic.Deployer command throws an exception for this missing configuration. If data source JNDI name referenced in the deployment descriptors of an EJB module is missing, then the initiated deployment task will fail on the targeted server with an exception javax.naming.NameNotFoundException but the weblogic.Deployer command-line tool hangs forever.

A timeout parameter needs to be added. However, this is not a valid step for the customer to use on every deployment when there will be multiple deployments.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.