Skip to Content
avatar image
Former Member

Undeplyoment of AE 5.2 - server restart - dispatcher doesn't start

Hi expertes,

yesterday I tried to undeply Access Control AE 5.2 using SDM. The undeployment process ran for several hours and finally I killed it. However, when I tried to log into JSPM to dpley AE 5.3 it was still locked by the admin user. So I decided to restart the instance and now the dispatcher doesn't start. I retrieved the following errors:

First, in \usr\sap\<SID>\DV\work\dev-w I find the following

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

[Thr 5824] Mon Sep 20 21:21:42 2010

[Thr 5824] JLaunchIExitJava: exit hook is called (rc = -11114)

[Thr 5824] **********************************************************************

  • ERROR => The Java VM terminated with a non-zero exit code.

  • Please see SAP Note 943602 , section 'J2EE Engine exit codes'

  • for additional information and trouble shooting.

**********************************************************************

[Thr 5824] JLaunchCloseProgram: good bye (exitcode = -11114)

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Log \usr\sap\<SID>\DVEBMGS00\j2ee\cluster\server0\log\system\ shows the following exception:

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Error occurred on server 1737650 during startApp sap.com/tcsldwdmain : com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ' 'sap.com/tcsldwdmain'' for startup. Reason=

Clusterwide exception: Failed to start application ''sap.com/tcsldwdmain'': The referenced application ''sap.com/tcsldwdtechnicalsystem'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?

at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)

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

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

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

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

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

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

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

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

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

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

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)

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Any ideas how to solve this issue ?

Kind regards

Max

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Sep 21, 2010 at 12:17 PM

    Hi,

    You should not have killed SDM process abruptly.

    Could you please dev_dispatcher and std_dispatcher log here ?

    Thanks

    Sunny

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Sunny,

      thanks again !

      As this is a sandbox test system I am not sure if a backup exists. Do you have an idea where the files are deployed (which directory) ? I am not familiar with SAP J2EE application server, but I had experience with websphere and weblogic some years ago. Maybe I am able to fix it via file system ?

      Regards,

      Max

  • avatar image
    Former Member
    Sep 22, 2010 at 08:46 AM

    sad but true, the restart of the whole server (windows environment) solved the issue.

    Add comment
    10|10000 characters needed characters exceeded