Page tree
Skip to end of metadata
Go to start of metadata

Category:Deployment failed

Problem

No available container

Keywords

  • Container is stopped
  • Container is not deployed
  • Container not active
  • Container webdynpro is not active at the moment and it is not possible to update....
  • [ERROR CODE DPL.DS.5082]

Symptoms

During deployment similar error occurs:

Container webdynpro is not active at the moment and it is not possible to update
sap.com/Hello


Caused by: java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException:
Error occurred while deploying ear file C:\Documents and Settings\C5072611\My Documents\Hello.ear.

Reason: Exception while validating application sap.com/Hello.

The sap.com/Hello application was processed from [app_libraries_container, EJBContainer, servlet_jsp,
SCA Composites Container] containers, but none of them returned information about deployed components.

The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume,
SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload,
servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer,
Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector,EJBContainer,
webservices_container, scheduler~container, Content Container]
Possible reasons :
1. Empty or incorrect application, which is not recognized by registered containers.
2. An AS Java service, which is providing a container, is stopped or not deployed.
3. The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info.

Solution

  1. You may check that all Containers, required for the deployment of the failed component, are running. For components of J2EE software type, the names of the necessary containers can be found in META-INF/application-j2ee-engine.xml inside the component's SDA archive.
  2. Faulty component contents (e.g. missing files) can be the first reason for the deployment failure.

To check the containers:

  • First, connect to the server via Telnet with your admin account.
  • Check if the AS Java service, which is providing a container, is deployed.
    To do this type:
    >container_info -a

As a result you will get a list of the names of all containers on servers in the cluster.
All available containers:
com.sap.security.ume
app_libraries_container
Cache Configuration Upload
servlet_jsp
dbcontentcontainer
connector
Cluster File System
MigrationContainer
JMSConnector
Monitoring Configurator
dbschemacontainer
appclient
orpersistence
Text Container
JDBCConnector
EJBContainer
webservices_container

  • Check if the J2EE service, which is providing a container, is started.
    To do this, first type:

>container_info -c <container_name>

so that you find out which service is responsible for this container, then type:

>lss | grep <service_name>

to see if this service is started.

  • Check if there are no filters that DISABLED the components you want to deploy.
    Read more how to apply Filters.

In general make sure that all the required containers are running and try to redeploy again.

Sample logs

17.01.2006 21:33:35 /userOut/daView_category
(eclipse.UserOutLocation) [Thread[Deploy Thread,6,main]]
ERROR: Deploy Exception.An error occurred while deploying the
deployment item 'local_JA310_Ex_2'.; nested exception is:
#java.rmi.RemoteException: class
com.sap.engine.services.dc.gd.DeliveryException: An error
occurred during deployment of sdu id: local_JA310_Ex_2
sdu file path: C:\usr\sap\A03\JC70\j2ee\cluster\server0
\temp\tc~bl~deploy_controller\archives\9\JA310_Ex_2.ear
version status: NEW
deployment status: Admitted
description: Error:
Cannot deploy application local/JA310_Ex_2..
Reason: Exception while validating application
local/JA310_Ex_2 : it has no container data..; nested exception is:
#java.rmi.RemoteException: class
com.sap.engine.services.deploy.server.utils.DSRemoteExceptio
n: Cannot deploy application local/JA310_Ex_2..
Reason: Exception while validating application
local/JA310_Ex_2 : it has no container data..; nested exception is:
#java.rmi.RemoteException: class
com.sap.engine.services.deploy.exceptions.ServerDeploymentE
xception: Exception while validating application
local/JA310_Ex_2 : it has no container data..
  • No labels