weblogic.Deployer Command Waits Forever if Deploy Fails on Managed Server
(Doc ID 1134176.1)
Last updated on JUNE 07, 2022
Applies to:Oracle WebLogic Server - Version 9.2 to 10.3.6
Information in this document applies to any platform.
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.
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