Skip to Content
author's profile photo Former Member
Former Member

Deployment Problem: Cannot update archive file

Hi!

I am trying to deploy an EAR for my Projekt "PegasusServerApp". The Application had been deployed on the server before but I removed it using remove_app on a telnet client. (and it is really gone! at least I cannot see it anymore in the visual administrator nor in the telnet client)

Another attempt to deploy the (re-worked) Application fails with com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file PegasusEJB.jar

What makes me suspicious is a detail from the deployment log: Update: Selected development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19' updates currently deployed development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.11.18.52'.

Why is it "currently deployed" when I removed it before?

Has anyone an idea what goes wrong?

Here is the complete deployment log: (from the Developer Studio)

02.12.2004 19:30:07 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Deploy Thread] INFO:

PegasusApp.ear -> Additional log information about the deployment

<! LOGHEADER[START]/ >

<! HELP[Manual modification of the header may cause parsing problem!]/ >

<! LOGGINGVERSION[1.5.3.7111 - 630_SP]/ >

<! NAME[C:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20041202182935.log]/ >

<! PATTERN[C:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20041202182935.log]/ >

<! FORMATTER[com.sap.tc.logging.TraceFormatter]/ >

<! LOGHEADER[END]/ >

Dec 2, 2004 7:29:37 PM Info: -


Starting deployment -


Dec 2, 2004 7:29:37 PM Info: Loading selected archives...

Dec 2, 2004 7:29:37 PM Info: Loading archive 'C:\usr\sap\J2E\JC00\SDM\program\temp\temp21072PegasusApp.ear'

Dec 2, 2004 7:29:44 PM Info: Selected archives successfully loaded.

Dec 2, 2004 7:29:44 PM Info: Actions per selected component:

Dec 2, 2004 7:29:44 PM Info: Update: Selected development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19' updates currently deployed development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.11.18.52'.

Dec 2, 2004 7:29:44 PM Info: Saved current Engine state.

Dec 2, 2004 7:29:44 PM Info: Error handling strategy: OnErrorStop

Dec 2, 2004 7:29:44 PM Info: Update strategy: UpdateAllVersions

Dec 2, 2004 7:29:44 PM Info: Starting: Update: Selected development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19' updates currently deployed development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.11.18.52'.

Dec 2, 2004 7:29:44 PM Info: SDA to be deployed: C:\usr\sap\J2E\JC00\SDM\root\origin\isenergy.de\PegasusServerApp\localhost\2004.12.02.19.02.19\temp21072PegasusApp.ear

Dec 2, 2004 7:29:44 PM Info: Software type of SDA: J2EE

Dec 2, 2004 7:29:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Dec 2, 2004 7:29:56 PM Info: Begin of log messages of the target system:

04/12/02 19:29:46 - ***********************************************************

04/12/02 19:29:53 - Start updating EAR file...

04/12/02 19:29:53 - start-up mode is lazy

04/12/02 19:29:56 - com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file PegasusEJB.jar

null. Reason:

at com.sap.engine.deploy.manager.DeployManagerImpl.makeTempEar(DeployManagerImpl.java:3755) at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewEar1(DeployManagerImpl.java:3721) at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:522) at com.sap.engine.deploy.manager.DeployManagerImpl.update(DeployManagerImpl.java:511) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:196) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96) at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224) at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60) at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186) at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46) at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83) at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60) at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:72) at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73) at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:127) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:96) at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38) at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:81) at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67) at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76) at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:280) at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43) at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39) at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50) at java.lang.Thread.run(Thread.java:534) 04/12/02 19:29:56 - *********************************************************** Dec 2, 2004 7:29:56 PM Info: End of log messages of the target system. Dec 2, 2004 7:29:56 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 2, 2004 7:29:56 PM Error: Aborted: development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19': Caught exception during application deployment from SAP J2EE Engine's deploy API: com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file PegasusEJB.jar null. Reason:

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

Dec 2, 2004 7:29:56 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Dec 2, 2004 7:29:56 PM Error: -


At least one of the Deployments failed -


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2004 at 11:01 AM

    Hi again!

    It appears that the problem is related to some resources within the PegasusEJB.jar: almost all resources like .xml files are neatly located unter rsrc/de/isnenergy/pegasus/... where they can be found by their corresponding classes. The classes have packages like de.isenergy.pegasus.... . Some resources, however, are located under rsrc/icons and there is no package icons. (don't ask me how they are found)

    this may be the reason! When I remove the icon-resources, I can deploy my EAR.

    agree?

    Jan-Peter

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Another update on this strange topic:

      The path where the icons can be found is irrelevant to the deployment failure. I have tried to put the icons under /de/isenergy/pegasus/icons/ instead of simply /icons - the deployment error remains.

      What does the deployment service do with the resources? Why can a deployment fail on a few icons?

      Jan-Peter

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.