Failed With: Could Not Get DeploymentManager When Deploying With admin_client.jar
(Doc ID 364692.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Oracle Containers for J2EE - Version 10.1.3.0.0 and laterOracle Fusion Middleware - Version 10.1.3.0.0 to 10.1.3.5.1 [Release AS10gR3]
Information in this document applies to any platform.
Symptoms
Unable to deploy using the admin_client.jar utility:
as it fails with error:
Failed at "Could not get DeploymentManager".
As well as with log file output of the file OC4J~home~default_group~1:
oracle.oc4j.admin.deploy.spi.exceptions.DeploymentRuntimeException: Cannot connect to any of the OC4J process(es) in the cluster
at oracle.oc4j.admin.deploy.spi.ClusterHelper.getLocalClusterDomain(ClusterHelper.java:353)
at oracle.oc4j.admin.deploy.spi.ClusterDeploymentManager.<init>(ClusterDeploymentManager.java:119)
Cause
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
Symptoms |
Cause |
Solution |
References |