Application Already In Use 

Problem Description

A deployment operation over an application finishes with an error message stating that another operation with this application has already been started:

Error: Already started operation with application

Scenario Type:	Error analysis
NetWeaver Component:	J2EE Engine Deployment (BC-JAS-DPL)
Validity:	J2EE version >= 6.30 on all supported platforms

Decision Roadmap

Prerequisites

-

Main Tools

SDM

Visual Administrator

Telnet

Analysis

Noticing the problem

In the SDM GUI 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:

java.rmi.RemoteException:

Already started operation with application sap.com/tc~dtr~enterpriseapp in the cluster.

No other operation over this application is allowed at the moment.

Reason: Can not lock [2004010715563630500000PWDF2004....................44050250,          

DEPLOY_LOCK_AREA, sap.com/tc~dtr~enterpriseapp, X],

because it is already used by the same owner;

nested exception is: #com.sap.engine.frame.core.locking.LockException:

Can not lock [2004010715563630500000PWDF2004....................44050250,          

DEPLOY_LOCK_AREA, sap.com/tc~dtr~enterpriseapp, X],

because it is already used by the same owner;

nested exception is: #com.sap.engine.frame.core.locking.LockException:

Can not lock [2004010715563630500000PWDF2004....................44050250,          

DEPLOY_LOCK_AREA, sap.com/tc~dtr~enterpriseapp, X],

because it is already used by the same owner  

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.      Click with the right mouse button to display a context menu.

       5.      Select Display file.

The content of the traces are displayed.

Possible reasons

●     A deployment operation over an application has been invoked before another deployment operation over the same application has finished.

●     Deploy, redeploy or update operation over application A is invoked. Application B has a reference to A. Deploy service stops application B internally and after application A has been started, deploy service tries to start application B. In the meantime another deployment operation over application B is invoked.

●     Redeploy of library is invoked. An application has a reference to this library, so it should be restarted. Meanwhile, another deployment operation is performed over the application.

Solution

Before starting a deployment operation over the application you should wait for the end of the previously started operation.

Additional Information

See note 710966