No Container Available For J2EE Module 

Problem Description

An application deployment fails with the following error message:

No available container for J2EE module <module_name>.

Scenario Type:	Error analysis
NetWeaver Component:	J2EE Engine
Validity:	J2EE version >= 6.30 on all supported platforms

Decision Roadmap

Prerequisites

-

Main Tools

SDM

Visual Administrator

Telnet

Analysis

Noticing the problem

When deploying or updating an application via SDM you get the following error:

If you do not use SDM but another tool for deploying (e.g. a Telnet session, the Visual Administrator or the Deploy Tool), you would find the following trace in the Deploy Service traces:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException:

Cannot deploy application sap.com/Appl.

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:635)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(Application

Transaction.java:301)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:332)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2945)

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:454)

at com.sap.engine.services.deploy.command.DeployCommand.exec(DeployCommand.java:247)

at com.sap.engine.services.shell.processor.environment.CommandBase.exec(CommandBase.java:132)

at com.sap.engine.services.shell.processor.Interpreter.applyLineCommand(Interpreter.java:391)

at com.sap.engine.services.shell.processor.Interpreter.apply(Interpreter.java:150)

at com.sap.engine.services.shell.processor.Shell.work(Shell.java:142)

at com.sap.engine.services.shell.processor.managers.ShellProcessThread.run(ShellProcessThread.java:113)

Caused by: com.sap.engine.services.deploy.ear.exceptions.BaseEarException:

No available container for J2EE module Web.war.

at com.sap.engine.services.deploy.ear.jar.EARReader.getAllContainerFiles(EARReader.java:576)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:544)

To view the Deploy Service traces we recommend using the Log Viewer.

...

       1.      Start the Visual Administrator.

       2.      Log in and select service Log Viewer.

       3.      Select defaultTrace.trc.

       4.      After a right mouse click, a context menu appears.

       5.      Select Display file.

The content of the traces is displayed.

Possible reasons

There is no container available for a module. This means that the corresponding container is not started. Most likely this is because the service providing the container has not been started.

Solution

Start the service which provides the stopped container. You can use the Visual Administrator or a Telnet session.

●     Start the Visual Administrator.

                            a.      Log in and select the corresponding service.

                            b.      After a right mouse click, a context menu appears.

                            c.      Select Start to start the service.

In the example bellow we are starting the Web Container.

●     Open a Telnet session.

                            a.      Log in and type jump 0 to go to the server.

                            b.      Type in startservice <corresponding_service_name>.

This starts the service.

In the example below we are starting the service servlet_jsp.

Starting the service starts the container it provides. Now you can retry deploying or updating the application.

Additional Information

Since Web AS 6.40 SP4 we differentiate between optional and obligatory containers.

Optional containers are the log configurator and the monitoring configurator, provided by service log_configurator and monitor respectively. Even if some of the optional containers are stopped, an application with modules for these containers could be deployed and will then work successfully.