cancel
Showing results for 
Search instead for 
Did you mean: 

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

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

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

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

You should not have killed SDM process abruptly.

Could you please dev_dispatcher and std_dispatcher log here ?

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny,

thanks in advance !

Regard, Max

Here you can find the last entries of dev_dispatcher

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

[Thr 600] Mon Sep 20 21:21:24 2010

[Thr 600] JLaunchISetHttpPort: set http port 50000

[Thr 600] JLaunchISetHttpsPort: set https port 50001

[Thr 600] JLaunchISetP4Port: set p4 port 50004

[Thr 600] Mon Sep 20 21:21:25 2010

[Thr 600] JLaunchISetTelnetPort: set telnet port 50008

[Thr 5136] Mon Sep 20 21:21:31 2010

[Thr 5136] JLaunchRequestFunc: receive command:17, argument:0 from pid:260

[Thr 5136] JLaunchIShutdownInvoke: set shutdown interval (stop:1285010491/end:1285010611/TO:120)

[Thr 5136] JLaunchProcessCommand: Invoke VM Shutdown

[Thr 5136] JHVM_FrameworkShutdownDirect: invoke direct shutdown

[Thr 4040] Mon Sep 20 21:21:32 2010

[Thr 4040] JLaunchISetP4Port: set p4 port 50004

[Thr 4720] JLaunchISetP4Port: set p4 port 50004

[Thr 5100] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]

[Thr 5100] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]

[Thr 4528] JLaunchISetHttpPort: set http port 50000

[Thr 4668] JLaunchISetHttpPort: set http port 50000

[Thr 4668] JLaunchISetHttpsPort: set https port 50001

[Thr 4528] JLaunchISetHttpsPort: set https port 50001

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

[Thr 4404] JLaunchISetP4Port: set p4 port 50004

[Thr 3148] Mon Sep 20 21:21:43 2010

[Thr 3148] JLaunchISetHttpPort: set http port 50000

[Thr 4260] JLaunchISetHttpPort: set http port 50000

[Thr 4040] Mon Sep 20 21:21:44 2010

[Thr 4040] JLaunchISetHttpsPort: set https port 50001

[Thr 4040] JLaunchISetHttpPort: set http port 50000

[Thr 2228] Mon Sep 20 21:21:51 2010

[Thr 2228] JLaunchISetTelnetPort: set telnet port 50008

[Thr 2180] Mon Sep 20 21:21:52 2010

[Thr 2180] JLaunchISetHttpPort: set http port 50000

[Thr 5100] Mon Sep 20 21:21:56 2010

[Thr 5100] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]

[Thr 4348] Mon Sep 20 21:21:59 2010

[Thr 4348] JLaunchIExitJava: exit hook is called (rc = 0)

[Thr 4348] JLaunchCloseProgram: good bye (exitcode = 0)

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

dev_dispatcher.b00

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

[Thr 4288] Wed Aug 25 21:07:58 2010

[Thr 4288] JLaunchIExitJava: exit hook is called (rc = 143)

[Thr 4288] **********************************************************************

      • 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 4288] JLaunchCloseProgram: good bye (exitcode = 143)

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

std_dispatcher.out

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

started at : Tue Sep 07 09:59:12 2010

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

[Thr 4268] MtxInit: 10000 0 0

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue

CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode

CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode

CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto

SAP J2EE Engine Version 7.00 PatchLevel 51441.450 is starting...

Loading: LogManager ... 3797 ms.

Loading: PoolManager ... 31 ms.

Loading: ThreadManager ... 94 ms.

Loading: IpVerificationManager ... 62 ms.

Loading: ConnectionsManipulator ... 63 ms.

Loading: ClassLoaderManager ... 31 ms.

Loading: ClusterManager ... 375 ms.

Loading: PortsManager ... 31 ms.

Loading: LockingManager ... 110 ms.

Loading: ConfigurationManager ... 5297 ms.

Loading: LicensingManager ... 47 ms.

Loading: CacheManager ... 187 ms.

Loading: ServiceManager ...

Loading services.:

[ParNew 58239K->3860K(174016K), 0.0487141 secs]

Service security started. (78 ms).

Service sld started. (15 ms).

Service timeout started. (31 ms).

Service memory started. (16 ms).

Service r3startup started. (31 ms).

Service licensing started. (0 ms).

Service httptunneling started. (94 ms).

Service webservices started. (141 ms).

Service keystore started. (32 ms).

Service jmx_notification started. (32 ms).

Service shell started. (422 ms).

Service ssl started. (156 ms).

Service telnet started. (313 ms).

Service jmx started. (500 ms).

Service iiop started. (4203 ms).

Service log_configurator started. (4125 ms).

Service configuration started. (0 ms).

Service jms_provider started. (484 ms).

Service basicadmin started. (515 ms).

Service adminadapter started. (15 ms).

Service p4 started. (6078 ms).

Service classload started. (16 ms).

Service http started. (1328 ms).

[ParNew 62083K->7408K(174016K), 0.0380524 secs]

Service tc.monitoring.logviewer started. (1078 ms).

Service monitor started. (1735 ms).

ServiceManager started for 10531 ms.

Framework started for 21484 ms.

SAP J2EE Engine Version 7.00 PatchLevel 51441.450 is running!

PatchLevel 51441.450 November 22, 2008 15:34 GMT

>

Login :[ParNew 65648K->9839K(174016K), 11.1240208 secs]

[ParNew 68079K->10089K(174016K), 0.5741166 secs]

[ParNew 68329K->10309K(174016K), 0.7268212 secs]

[ParNew 68549K->11815K(174016K), 2.2532700 secs]

[ParNew 70055K->12036K(174016K), 0.1960817 secs]

[ParNew 70276K->12245K(174016K), 0.7187775 secs]

[ParNew 70485K->12478K(174016K), 1.8292483 secs]

[ParNew 70718K->12669K(174016K), 1.4065374 secs]

[ParNew 70909K->12868K(174016K), 0.0838437 secs]

[ParNew 71108K->13126K(174016K), 1.5431157 secs]

[ParNew 71366K->13337K(174016K), 0.0140865 secs]

[ParNew 71577K->13547K(174016K), 0.1749310 secs]

[ParNew 71787K->13796K(174016K), 0.0335507 secs]

[ParNew 72036K->14044K(174016K), 1.3082749 secs]

[ParNew 72284K->14243K(174016K), 0.0323234 secs]

[ParNew 72483K->14448K(174016K), 2.5461057 secs]

[ParNew 72688K->14686K(174016K), 0.0451944 secs]

[ParNew 72926K->14927K(174016K), 0.0177763 secs]

[ParNew 73167K->15159K(174016K), 1.4635414 secs]

[ParNew 73399K->15394K(174016K), 0.0329669 secs]

[ParNew 73634K->15609K(174016K), 2.1897883 secs]

[ParNew 73849K->15840K(174016K), 0.0295903 secs]

[ParNew 74080K->16042K(174016K), 1.3180385 secs]

[ParNew 74259K->16259K(174016K), 2.7250196 secs]

[ParNew 74498K->16442K(174016K), 0.0350658 secs]

[ParNew 74682K->16656K(174016K), 1.5182675 secs]

[ParNew 74896K->16852K(174016K), 0.0202625 secs]

[ParNew 75092K->17064K(174016K), 0.7320056 secs]

[ParNew 75304K->17323K(174016K), 0.0395468 secs]

[ParNew 75563K->17566K(174016K), 1.7953515 secs]

[ParNew 75806K->18247K(174016K), 0.3988221 secs]

SAP J2EE Engine Version 7.00 PatchLevel 51441.450 is shutting down! PatchLevel 51441.450 November 22, 2008 15:34 GMT

Stopping services.

Service classload stopped. (1609 ms)

Service tc.monitoring.logviewer stopped. (4344 ms)

Service p4 stopped. (1219 ms)

Service ssl stopped. (719 ms)

Service keystore stopped. (141 ms)

Service iiop stopped. (3000 ms)

Service adminadapter stopped. (109 ms)

Service monitor stopped. (891 ms)

Service security stopped. (15 ms)

Service basicadmin stopped. (297 ms)

Service jms_provider stopped. (1016 ms)

Service jmx stopped. (16 ms)

Service webservices stopped. (31 ms)

Service sld stopped. (16 ms)

Service telnet stopped. (1109 ms)

Service http stopped. (1031 ms)

Service timeout stopped. (31 ms)

Service configuration stopped. (140 ms)

Service log_configurator stopped. (47 ms)

Service memory stopped. (16 ms)

Service r3startup stopped. (63 ms)

Service licensing stopped. (0 ms)

Service httptunneling stopped. (16 ms)

Service shell stopped. (16 ms)

Service jmx_notification stopped. (16 ms)

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

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

> [Thr 4288] JLaunchIExitJava: exit hook is called (rc = 143)

> [Thr 4288] **********************************************************************

> *** 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 4288] JLaunchCloseProgram: good bye (exitcode = 143)

The file shows that Engine Exit with exitcode = 143,which means that there is some configuration missing .Not much information is

available in other files attached. Check default trace file.

As I think u killed the SDM process in between, so files related to AE is in inconsistent status. I would suggest whether to restore file system backup prior to undeploy of files or raise it to SAP.

Thanks

Sunny

Former Member
0 Kudos

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