Problem Deploy application "stopping"

[Former Member]

Hi , Iu00B4m getting this error when I tried to deploy and application in my portal server

ov 8, 2007 4:49:47 PM Info: -

---

Starting deployment -

---

Nov 8, 2007 4:49:47 PM Info: Error handling strategy: OnErrorStop

Nov 8, 2007 4:49:47 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop

Nov 8, 2007 4:49:47 PM Info: Update strategy: UpdateAllVersions

Nov 8, 2007 4:49:47 PM Info: Starting deployment prerequisites:

Nov 8, 2007 4:49:56 PM Info: Loading selected archives...

Nov 8, 2007 4:49:56 PM Info: Loading archive 'G:\usr\sap\EPD\JC00\SDM\program\temp\temp44551borrar.ear'

Nov 8, 2007 4:49:59 PM Info: Selected archives successfully loaded.

Nov 8, 2007 4:50:00 PM Info: Actions per selected component:

Nov 8, 2007 4:50:00 PM Info: Update: Selected development component 'borrar'/'local'/'LOKAL'/'0.2007.11.08.22.53.05'/'0' updates currently deployed development component 'borrar'/'local'/'LOKAL'/'0.2007.11.08.22.06.59'/'0'.

Nov 8, 2007 4:50:00 PM Info: Ending deployment prerequisites. All items are correct.

Nov 8, 2007 4:50:00 PM Info: Saved current Engine state.

Nov 8, 2007 4:50:00 PM Info: Starting: Update: Selected development component 'borrar'/'local'/'LOKAL'/'0.2007.11.08.22.53.05'/'0' updates currently deployed development component 'borrar'/'local'/'LOKAL'/'0.2007.11.08.22.06.59'/'0'.

Nov 8, 2007 4:50:00 PM Info: SDA to be deployed: G:\usr\sap\EPD\JC00\SDM\root\origin\local\borrar\LOKAL\0\0.2007.11.08.22.53.05\temp44551borrar.ear

Nov 8, 2007 4:50:00 PM Info: Software type of SDA: J2EE

Nov 8, 2007 4:50:00 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Nov 8, 2007 5:00:31 PM Info: Begin of log messages of the target system:

07/11/08 16:50:01 - ***********************************************************

07/11/08 16:50:11 - Start updating EAR file...

07/11/08 16:50:11 - start-up mode is lazy

07/11/08 16:50:12 - EAR file updated successfully for 1391ms.

07/11/08 16:50:12 - Start updating...

07/11/08 16:50:29 - EAR file uploaded to server for 4797ms.

07/11/08 17:00:31 - ERROR: Not updated. Deploy Service returned ERROR:

java.rmi.RemoteException: Already started operation with application local/borrar in the cluster. No other operation with this application is allowed at the moment..

Reason: Cannot lock [2007110815392386800000server_portal..................6139650, DEPLOY_LOCK_AREA, local/borrar, X]; it is in use by the same owner. In case of lock mode "R" the lock propagation failed, because the optimistic lock is gone.; nested exception is:

com.sap.engine.frame.core.locking.LockException: Cannot lock [2007110815392386800000server_portal..................6139650, DEPLOY_LOCK_AREA, local/borrar, X]; it is in use by the same owner. In case of lock mode "R" the lock propagation failed, because the optimistic lock is gone.

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

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2007110815392386800000server_portal..................6139650, DEPLOY_LOCK_AREA, local/borrar, X]; it is in use by the same owner. In case of lock mode "R" the lock propagation failed, because the optimistic lock is gone.

at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:263)

at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:421)

at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:1090)

at com.sap.engine.services.deploy.server.TransactionManager.lockApplication(TransactionManager.java:139)

at com.sap.engine.services.deploy.server.TransactionManager.registerTransactionWithLock(TransactionManager.java:89)

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

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

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

... 10 more

For detailed information see the log file of the Deploy Service.

07/11/08 17:00:31 - ***********************************************************

Nov 8, 2007 5:00:31 PM Info: End of log messages of the target system.

Nov 8, 2007 5:00:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Nov 8, 2007 5:00:31 PM Error: Aborted: development component 'borrar'/'local'/'LOKAL'/'0.2007.11.08.22.53.05'/'0':

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Already started operation with application local/borrar in the cluster. No other operation with this application is allowed at the moment..

Reason: Cannot lock [2007110815392386800000server_portal..................6139650, DEPLOY_LOCK_AREA, local/borrar, X]; it is in use by the same owner. In case of lock mode "R" the lock propagation failed, because the optimistic lock is gone.; nested exception is:

com.sap.engine.frame.core.locking.LockException: Cannot lock [2007110815392386800000server_portal..................6139650, DEPLOY_LOCK_AREA, local/borrar, X]; it is in use by the same owner. In case of lock mode "R" the lock propagation failed, because the optimistic lock is gone.

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Nov 8, 2007 5:00:31 PM Info: Starting to save the repository

Nov 8, 2007 5:00:34 PM Info: Finished saving the repository

Nov 8, 2007 5:00:34 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Nov 8, 2007 5:00:34 PM Error: -

---

At least one of the Deployments failed -

---

The current status of my application:

Making a telnet : get_status -a name_app -> return state: STOPPING I tried stopped it through visual administrator also deleting ear file and rebuild but I'm getting the error again.

Can you please give me a hint!!

Thanks

Thanks

[Former Member]

Hi Maria

1) Try to undeploy your existing .EAR file

2) Deply again

3) Restart both the cluster and the J2EE server

Best Regards

Chaitanya.A

[Former Member]

Hi thanks to you both!

Chaitanya: I tried to undeploy my EAR and the server took a long time to do it even my application only has a text view and a buttom.

Then i decided made what Dennis proposed, the deploy was successfully but now my iview is not reached the server hangs trying to shows the iview.

telnet to application status again: "STOPPING"

Then I made a new deploy and the same error appears (last trace pasted)

I check this thread but I don´t understand the solution I use Oracle Database

Any help?

Thanks a lot

[Former Member]

Hi,

have you tried to restart the Cluster after removing the EAR File. It's maybe not enough just to restart the server node.

Regards,

Dennis