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

Problem

Upgrade fails at SHD_ONLINE_DEPLOYMENT phase. In traces deployment of SEACORE00_0-20010046_SCA13437272744 fails, because it cannot look up JMS queues and ends with a name not found Exception.

Keywords

• SEACORE
• EP-ADMIN
• wizard_framework
• sap.com_tc~esi~sea~content
• sap.com_tc~esi~sea~core~ear

Symptoms

In "DEPLOY_ONLINE_SHD_DM" phase fails deployment of:
SEACORE00_0-20010046.SCA > tc~esi~sea~content.sda
The deployment of [sap.com_tc~esi~sea~content] failed, because application [sap.com_tc~esi~sea~core~ear] was skipped.

Root cause for the skipping of this application is that during online phase the deployment of some component has failed. After the error all online items are skipped.

In some frequent cases [sap.com_tc~esi~sea~core~ear] is skipped because
- [Aborted] : sap.com_EP-ADMIN,
   - [Aborted] : sap.com_wizard_framework.

Solution

  • Deploy manually [sap.com/tc~esi~sea~proxies~ear] and [sap.com_tc~esi~sea~core~ear] from SEACORE.SCA
  • Continue the step in SUM tool;
  • Create CSN in corresponding component for the root cause of the issue, which is failure of sap.com_wizard_framework or another component in "Online Deployment" phase. See the deploy.0.trc and deploy.0.log traces from "work" folder for details.

Sample logs

Deployment in Post-Online phase fails with the following Exception:

Caused by: com.sap.engine.services.content.handler.api.exception.ContentHandlerException: 
Cannot lookup jms queue [jmsqueues/default/SeaContentPreload] or jms factory [jmsfactory/default/SeaConnectionFactory]
 at com.sap.engine.services.sea.deploy.DeployTransaction.createAndSendMessage(DeployTransaction.java:186)
 at com.sap.engine.services.sea.deploy.DeployTransaction.sendMessages(DeployTransaction.java:166)
 at com.sap.engine.services.sea.deploy.DeployTransaction.begin(DeployTransaction.java:98)
 at com.sap.engine.services.content.container.ContentContainer.performContentDeploymentTransactions(ContentContainer.java:1252)
... 23 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of SeaContentPreload.
 at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:630)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:363)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:655)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at com.sap.engine.services.sea.deploy.DeployTransaction.createAndSendMessage(DeployTransaction.java:182)
 ... 26 more

/usr/sap/SUM_SP03/SUM/java/QE1/JC02/work/deploy.0.trc file could contain:

com.sap.ds.core.exceptions.PersistencyException: Error while checking
existence of configuration at sap.com_wizard_framework
 at com.sap.ds.core.persistency.impl.ConfigurationFileSystem.exists(ConfigurationFileSystem.java:481)
 at com.sap.ds.core.persistency.impl.ConfigurationFileSystem.exists(ConfigurationFileSystem.java:1592)
 at com.sap.ds.core.container.handler.buildspace.BuildSpaceUpdationNotifier.doAction(BuildSpaceUpdationNotifier.java:82)
 at com.sap.ds.core.container.handler.buildspace.BuildSpaceHandler.deploy(BuildSpaceHandler.java:66)
 at com.sap.ds.core.container.impl.DevelopmentServiceContainer.deploy(DevelopmentServiceContainer.java:239)

In this case – deploy part of Visual Composer (VCFRAMEWORK00_0-20010063.SCA -> vc_ds_service.sda), shall trace in their location what was the real cause for the failure.

Related SAP Notes

N/A

Related CSNs

3240450 2012
3660493 2011
0060056 2011
2326159 2010
2305863 2010
2045010 2010
1889310 2010
3384373 2009

  • No labels