Runtime Workbench "503 Service Unavailable" Error After JSPM SP Update

[Former Member]

Hi Experts,

We have been struggling with the following issue and your help would be greatly appreciated.

We have PI 7.1 with SPS 5. We applied the Message Service 7.10 SP5 with latest patch 17 into our PI environment using the JSPM (SP5 Patch 1). Following this patch application, we are getting "503 Service Unavailable" error when we try to launch the Runtime Workbench, which displays the following error:

-

---

Application cannot be started!

Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application sap.com/com.sap.xi.rwb cannot be started. Reason: it has hard reference to resource com.sap.xi.mdt.beans with type application, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:843)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:580)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:411)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:498)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

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

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

at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)

at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)

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:152)

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

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while preparing start of application sap.com/com.sap.xi.mdt.beans.

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:229)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:185)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:491)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:256)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:400)

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

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

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:835)

... 35 more

Caused by: java.lang.NoClassDefFoundError: com/sap/aii/mdt/server/adapterframework/proxy/OperationFailedException

at java.lang.Class.getDeclaredMethods0(Native Method)

at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)

at java.lang.Class.privateGetPublicMethods(Class.java:2519)

at java.lang.Class.getMethods(Class.java:1406)

at com.sap.engine.services.ejb3.runtime.MethodsTable.<init>(MethodsTable.java:30)

at com.sap.engine.services.ejb3.runtime.impl.AbstractComponentInterfaceFactory.<init>(AbstractComponentInterfaceFactory.java:55)

at com.sap.engine.services.ejb3.runtime.impl.Actions_SessionBeanFactoriesInitialization.createServiceEndpointInterfaceFactory(Actions_SessionBeanFactoriesInitialization.java:75)

at com.sap.engine.services.ejb3.runtime.impl.Actions_SessionBeanFactoriesInitialization.perform(Actions_SessionBeanFactoriesInitialization.java:55)

at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)

at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:425)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)

... 42 more

Caused by: java.lang.ClassNotFoundException: com.sap.aii.mdt.server.adapterframework.proxy.OperationFailedException

-

---

Loader Info -

---

ClassLoader name: [sap.com/com.sap.xi.mdt.beans]

Living status: alive

Direct parent loaders:

[system:Frame]

[service:servlet_jsp]

[service:ejb]

[library:engine.j2ee14.facade]

[library:com.sap.base.technology.facade]

[service:engine.application.facade]

[library:engine.rprof.dbprofiles.lib.facade]

[sap.com/com.sap.aii.af.ms.app]

[library:com.sap.xi.rwb.api]

[library:com.sap.aii.af.sdk.lib]

[library:com.sap.xi.mdt.api]

Resources:

/usr/sap/PD1/DVEBMGS11/j2ee/cluster/apps/sap.com/com.sap.xi.mdt.beans/EJBContainer/applicationjars/com_sap.xpi.mdt.afbean.jar

/usr/sap/PD1/DVEBMGS11/j2ee/cluster/apps/sap.com/com.sap.xi.mdt.beans/webservices_container/wsClients/app_jars/com.sap.xpi.mdt.wsmod.jar

-

---

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:259)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:228)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:353)

... 55 more

-

---

When we look at the j2ee applications, com.sap.xi.mdt.beans service is down and we cannot get it started. This is one of the components which seems to have been updated when Messaging Service 7.10 (SP5.17) was applied.

Any help and guidance to reaching a resolution would be much appreciated.

Cheers

Nam

[kenny_scott]

for release PI 7.1 the Adapter Framework component has a dependency on the Messaging System Service component therefore it is always adviseable to apply the latest patches for both components,

[#1335523 FAQ: Deployment PI Patches in Release 7.1 and higher|http://service.sap.com/sap/support/notes/1335523]

[jyothi_anagani]

Hi,

Because of J2EE application com.sap.aii.af.ms.app not active

Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine

The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.

Thanks.