cancel
Showing results for 
Search instead for 
Did you mean: 

J2ee engine not coming

Former Member
0 Kudos

Hi

After restart the java engine, system is not coming up, dis is running , server0 is not coming up, i am pasting the log trc.file

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

          at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)

          at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)

#

#1.5 #C66C810C6202004900000002007400B60004C6D6BD0DA459#1344525503931#com.sap.sldserv.comm.BridgeCommunicationHTTP##com.sap.sldserv.comm.BridgeCommunicationHTTP####n/a##7609b84be23511e1bb350000007ef113#SAPEngine_System_Thread[impl:5]_28##0#0#Error#1#/System/Server/SLDService#Plain###Error while sending HTTP data. Status: 401. Message: Unauthorized. Please check if the target SLD system is available and the SLD bridge is started there.#

#1.5 #C66C810C6202004100000162007400B60004C6D6BECA038B#1344525533053#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n/a##d7013d65e23411e1c13a0000007ef113#SAPEngine_System_Thread[impl:5]_35##0#0#Error#1#/System/Server#Plain###Error occurred while initially starting application sap.com/tc~slm~slmapp:According to the O/R mapping described in /META-INF/persistent.xml, a CMPBean intends to store its persistent information in table BC_SLM_SDT_SRV_GRP. Such table does not exist in the database. Create it before trying to start the application.#

#1.5 #C66C810C6202007500000000007400B60004C6DAADFC1C4E#1344542430993#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##dddba19ce25c11e1a0e30000007ef113#Thread[ExecutionRunner_433,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]No DB schema found for DB Database: id=PX2, name=PX2, vendor=DB2 UDB FOR UNIX AND WINDOWS, release=09.07.0003, creation_date=Wed Oct 06 06:00:00 CDT 1971#

#1.5 #C66C810C6202007500000001007400B60004C6DAAE071214#1344542431711#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##dddba19ce25c11e1a0e30000007ef113#Thread[ExecutionRunner_433,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Empty Soft Comp List returned for TS Java Technical System: id=PX2~JAVA, long_sid=PX2, install_number=0020071327, type=Java, sid=PX2, source=Sld, creation_date=Wed Oct 27 21:00:53 CDT 2010 and MI Main Instance: id=01200314690800000134~13, name=Adobe Document Services, p_ppms_id=01200314690800000134, m_ppms_id=13, creation_date=Wed Oct 06 06:00:00 CDT 1971#

#1.5 #C66C810C6202007500000002007400B60004C6DAAE0969DC#1344542431865#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##dddba19ce25c11e1a0e30000007ef113#Thread[ExecutionRunner_433,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Empty Soft Comp List returned for TS Java Technical System: id=PX2~JAVA, long_sid=PX2, install_number=0020071327, type=Java, sid=PX2, source=Sld, creation_date=Wed Oct 27 21:00:53 CDT 2010 and MI Main Instance: id=01200314690800000134~2, name=Application Server Java, p_ppms_id=01200314690800000134, m_ppms_id=2, creation_date=Fri Jun 10 08:44:56 CDT 2005#

#1.5 #C66C810C6202007500000003007400B60004C6DAAE0B7383#1344542431998#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##dddba19ce25c11e1a0e30000007ef113#Thread[ExecutionRunner_433,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Empty Soft Comp List returned for TS Java Technical System: id=PX2~JAVA, long_sid=PX2, install_number=0020071327, type=Java, sid=PX2, source=Sld, creation_date=Wed Oct 27 21:00:53 CDT 2010 and MI Main Instance: id=01200314690800000134~7, name=Enterprise Portal, p_ppms_id=01200314690800000134, m_ppms_id=7, creation_date=Tue Mar 30 10:46:58 CST 2004#

#1.5 #C66C810C6202007500000004007400B60004C6DAAE1305BD#1344542432494#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##dddba19ce25c11e1a0e30000007ef113#Thread[ExecutionRunner_433,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Empty Soft Comp List returned for TS Java Technical System: id=PX2~JAVA, long_sid=PX2, install_number=0020071327, type=Java, sid=PX2, source=Sld, creation_date=Wed Oct 27 21:00:53 CDT 2010 and MI Main Instance: id=01200314690800000134~46, name=EP Core - Application Portal, p_ppms_id=01200314690800000134, m_ppms_id=46, creation_date=Wed Sep 20 13:26:51 CDT 2006#

#1.5 #C66C810C6202007500000005007400B60004C6DAAE1C72A1#1344542433112#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##dddba19ce25c11e1a0e30000007ef113#Thread[ExecutionRunner_433,5,ExecMgrThreadGroup]##0#0#Error##Java###[Setup]A failure occured while connecting to ABAP stack on localhost sys=00 client=001 user=DDIC

[EXCEPTION]

{0}#1#com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts

          at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)

          at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)

          at com.sap.mw.jco.JCO$Client.connect(JCO.java:3279)

          at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:527)

          at com.sap.sup.admin.setup.DbaRfcAdapter.getJcoClient(DbaRfcAdapter.java:81)

          at com.sap.sup.admin.setup.DbaRfcAdapter.solmanCheckSystem(DbaRfcAdapter.java:109)

          at com.sap.sup.admin.setup.SapCluster.gatherDbcName(SapCluster.java:549)

          at com.sap.sup.admin.setup.LandscapeAdapter.loadSapCluster(LandscapeAdapter.java:516)

          at com.sap.sup.admin.setup.LandscapeAdapter.loadSapClusterFromTS(LandscapeAdapter.java:106)

          at com.sap.sup.admin.selfcheck.checks.setup.MonitoredInputCheck.process(MonitoredInputCheck.java:66)

          at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

          at java.lang.reflect.Method.invoke(Method.java:391)

          at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)

          at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)

          at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)

          at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)

          at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)

          at java.lang.Thread.run(Thread.java:770)

#

#1.5 #C66C810C6202007600000000007400B60004C6DAAEB9B645#1344542443418#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e58ef2efe25c11e1bb650000007ef113#Thread[ExecutionRunner_447,5,ExecMgrThreadGroup]##0#0#Error##Java###[Setup]A failure occured while connecting to ABAP stack on localhost sys=00 client=001 user=DDIC

[EXCEPTION]

{0}#1#com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts

          at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)

          at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)

          at com.sap.mw.jco.JCO$Client.connect(JCO.java:3279)

          at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:527)

          at com.sap.sup.admin.setup.DbaRfcAdapter.getJcoClient(DbaRfcAdapter.java:81)

          at com.sap.sup.admin.setup.DbaRfcAdapter.solmanCheckSystem(DbaRfcAdapter.java:109)

          at com.sap.sup.admin.setup.SapCluster.gatherDbcName(SapCluster.java:549)

          at com.sap.sup.admin.setup.LandscapeAdapter.loadSapCluster(LandscapeAdapter.java:516)

          at com.sap.sup.admin.setup.LandscapeAdapter.loadSapClusterFromTS(LandscapeAdapter.java:106)

          at com.sap.sup.admin.selfcheck.checks.setup.MonitoredInputCheck.process(MonitoredInputCheck.java:66)

          at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

          at java.lang.reflect.Method.invoke(Method.java:391)

          at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)

          at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)

          at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)

          at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)

          at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)

          at java.lang.Thread.run(Thread.java:770)

#

#1.5 #C66C810C6202007600000001007400B60004C6DAAEBEC776#1344542443751#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e58ef2efe25c11e1bb650000007ef113#Thread[ExecutionRunner_447,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=The JVM startup parameters were already properly set. Status=0 TS=1274371861465#

#1.5 #C66C810C6202007600000002007400B60004C6DAAEBEC8E0#1344542443751#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e58ef2efe25c11e1bb650000007ef113#Thread[ExecutionRunner_447,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=SSO setup OK Status=0 TS=1274371847732#

#1.5 #C66C810C6202007600000003007400B60004C6DAAEBEC9E5#1344542443751#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e58ef2efe25c11e1bb650000007ef113#Thread[ExecutionRunner_447,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=Http log settings are set for Http Analysis Status=0 TS=1274371866650#

#1.5 #C66C810C6202007600000004007400B60004C6DAAEBECAE3#1344542443752#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e58ef2efe25c11e1bb650000007ef113#Thread[ExecutionRunner_447,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=Support roles successfully assigned Status=0 TS=1274371856041#

#1.5 #C66C810C6202007700000000007400B60004C6DAAF1A5E09#1344542449753#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Empty Soft Comp List returned for TS Java Technical System: id=SMT~JAVA, long_sid=SMT, install_number=0020191026, type=Java, sid=SMT, source=Sld, creation_date=Fri May 14 10:13:13 CDT 2010 and MI Main Instance: id=01200615320800000636~5, name=Agents for managed systems, p_ppms_id=01200615320800000636, m_ppms_id=5, creation_date=Wed Oct 06 06:00:00 CDT 1971#

#1.5 #C66C810C6202007700000001007400B60004C6DAAF262360#1344542450524#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Empty Soft Comp List returned for TS Java Technical System: id=SMT~JAVA, long_sid=SMT, install_number=0020191026, type=Java, sid=SMT, source=Sld, creation_date=Fri May 14 10:13:13 CDT 2010 and MI Main Instance: id=01200615320800000636~6, name=Wily Introscope, p_ppms_id=01200615320800000636, m_ppms_id=6, creation_date=Wed Oct 06 06:00:00 CDT 1971#

#1.5 #C66C810C6202007700000002007400B60004C6DAAF2A9237#1344542450815#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Error##Java###[Setup]A failure occured while connecting to ABAP stack on localhost sys=00 client=001 user=DDIC

[EXCEPTION]

{0}#1#com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts

          at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)

          at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)

          at com.sap.mw.jco.JCO$Client.connect(JCO.java:3279)

          at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:527)

          at com.sap.sup.admin.setup.DbaRfcAdapter.getJcoClient(DbaRfcAdapter.java:81)

          at com.sap.sup.admin.setup.DbaRfcAdapter.solmanCheckSystem(DbaRfcAdapter.java:109)

          at com.sap.sup.admin.setup.SapCluster.gatherDbcName(SapCluster.java:549)

          at com.sap.sup.admin.setup.LandscapeAdapter.loadSapCluster(LandscapeAdapter.java:516)

          at com.sap.sup.admin.setup.LandscapeAdapter.loadSapClusterFromTS(LandscapeAdapter.java:106)

          at com.sap.sup.admin.selfcheck.checks.setup.MonitoredInputCheck.process(MonitoredInputCheck.java:66)

          at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)

          at sun.reflect.GeneratedMethodAccessor272.invoke(Unknown Source)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)

          at java.lang.reflect.Method.invoke(Method.java:391)

          at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)

          at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)

          at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)

          at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)

          at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)

          at java.lang.Thread.run(Thread.java:770)

#

#1.5 #C66C810C6202007700000003007400B60004C6DAAF2F04A9#1344542451106#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=Communication user SMDAGENT_SMP (password=********) was successfully created or checked at ABAP Host=sapsmt sys=00 client=001 Status=0 TS=1274371833692#

#1.5 #C66C810C6202007700000004007400B60004C6DAAF2F0611#1344542451107#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=ABAP profiles were successfully assigned to user SOLMANSID001 in ABAP user store at ABAP Host=sapsmt sys=00 client=001 Status=0 TS=1274371832859#

#1.5 #C66C810C6202007700000005007400B60004C6DAAF2F070F#1344542451107#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=The ABAP profile of instance sapsmt/SMT/00[CI] (sapsmt) contains the parameter : login/accept_sso2_ticket=1 Status=0 TS=1274371834092#

#1.5 #C66C810C6202007700000006007400B60004C6DAAF2F080E#1344542451107#com.sap.smd.server#sap.com/tc~webadministrator~scheduler~ejb#com.sap.smd.server#J2EE_GUEST#0##n/a##e9d8beb5e25c11e1ceb30000007ef113#Thread[ExecutionRunner_450,5,ExecMgrThreadGroup]##0#0#Warning##Plain###[Setup]Instance: sapsmt/SMT/00[CI] (sapsmt). Found SetupMessage in persistence, which does not map to a current step. Instance definition may have changed since last setup. SetupMessage=SetupMsg : Id=null Msg=User SAPSUPPORT was successfully created or checked, with support roles and profiles. Status=0 TS=1274371828682#

#1.5 #C66C810C6202006C0000000F007400B60004C6DABE88A6C7#1344542708639#com.sap.engine.core.licensing##com.sap.engine.core.licensing.checkLicense(swProduct)#J2EE_ADMIN#618##n/a##a09c8169e23711e1a55f0000007ef113#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1#/System/Server#Java###The installed license for software product "{0}" is NOT valid. The concerned component may only run with restricted functionality. In case of "J2EE-Engine" the system will shut down.#1#Maintenance_#

#1.5 #C66C810C6202007900000001007400B60004C6DB0A1D205C#1344543976661#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper####n/a##7859688ae26011e187040000007ef113#SAPEngine_System_Thread[impl:5]_2##0#0#Error##Plain###Service webdynpro error com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to access Web Dynpro container. during shutdown.#

#1.5 #C66C810C6202007900000003007400B60004C6DB0A1D238D#1344543976661#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper.ServiceStopper.run####n/a##7859688ae26011e187040000007ef113#SAPEngine_System_Thread[impl:5]_2##0#0#Error#1#/System/Server#Plain###Failed to access Web Dynpro container.#

#1.5 #C66C810C6202007900000004007400B60004C6DB0A1D2425#1344543976662#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper.ServiceStopper.run####n/a##7859688ae26011e187040000007ef113#SAPEngine_System_Thread[impl:5]_2##0#0#Error##Plain###com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to access Web Dynpro container.#

#1.5 #C66C810C6202007900000005007400B60004C6DB0A1D24BC#1344543976662#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper.ServiceStopper.run####n/a##7859688ae26011e187040000007ef113#SAPEngine_System_Thread[impl:5]_2##0#0#Error##Plain###com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to access Web Dynpro container.

          at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DOContainerHook.stop(DOContainerHook.java:76)

          at com.sap.engine.services.webdynpro.WebDynproFrame.stopInternal(WebDynproFrame.java:218)

          at com.sap.engine.services.webdynpro.WebDynproFrame.stop(WebDynproFrame.java:202)

          at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)

          at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

          at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)

          at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)

Caused by: java.lang.NullPointerException

          at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DOContainerHook.stop(DOContainerHook.java:73)

          ... 6 more

#

#1.5 #C66C810C6202003800000039007400B60004C6DB0A6689E1#1344543981472#com.sap.engine.services.servlets_jsp.Service##com.sap.engine.services.servlets_jsp.Service####n/a##79c0f0a2e26011e188750000007ef113#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###application [] Cannot lookup Deploy service. The error is: java.lang.ClassCastException: $Proxy178 incompatible with com.sap.engine.services.deploy.DeployService

          at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.unregisterDeployCallbackListener(ServletsAndJspServerFrame.java:545)

          at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:261)

          at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)

          at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

          at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)

          at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)

#

#1.5 #C66C810C620200380000003B007400B60004C6DB0A668CB9#1344543981472#com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame##com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame####n/a##79c0f0a2e26011e188750000007ef113#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###application [] Cannot lookup Deploy service.

The error is: java.lang.ClassCastException: $Proxy178 incompatible with com.sap.engine.services.deploy.DeployService

Exception id: [C66C810C6202003800000039007400B60004C6DB0A6689E1]#

#1.5 #C66C810C6202004100000163007400B60004C6DB0A6EDC89#1344543982017#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#/System/Server/CTC#Plain###Stopping Configuration util service...#

#1.5 #C66C810C6202004100000165007400B60004C6DB0A6EDDA3#1344543982017#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#/System/Server/CTC#Plain###Config util service stopped successfully.#

#1.5 #C66C810C6202002800000059007400B60004C6DB0A7154F2#1344543982179#com.sap.engine.services.security.policyconfiguration##com.sap.engine.services.security.policyconfiguration#######SAPEngine_System_Thread[impl:5]_65##0#0#Warning#1#/System/Security/PolicyConfiguration#Java###Exception occurred during unregister of policy configuration [{0}].

[EXCEPTION]

{1}#2#service.iiop#com.sap.engine.frame.core.configuration.ConfigurationException: Configuration security/configurations is not valid - configuration is closed.

          at com.sap.engine.core.configuration.impl.WriteAccessConfiguration.validityCheck(WriteAccessConfiguration.java:223)

          at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:713)

          at com.sap.engine.services.security.server.PolicyConfigurations.unregisterPolicyConfiguration(PolicyConfigurations.java:245)

          at com.sap.engine.services.iiop.server.CorbaServiceFrame.stop(CorbaServiceFrame.java:104)

          at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)

          at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

          at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)

          at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)

#

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member191911
Contributor
0 Kudos

The installed license for software product "{0}" is NOT valid.

Former Member
0 Kudos

i installed new licenses,and system restarted.before i upgrade latest kernel

sysno      00

sid        SID

systemid   324 (IBM RS/6000 with AIX)

relno      7010

patchlevel 0

patchno    176

intno      20020600

make:      single threaded, Unicode, 64 bit, optimized

pid        5374052

kernel runs with dp version 246000(ext=110000) (@(#) DPLIB-INT-VERSION-246000-UC

)

length of sys_adm_ext is 576 bytes

*** SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 5374052) [dpxxdisp.c   1311]

        shared lib "dw_xml.so" version 176 successfully loaded

        shared lib "dw_xtc.so" version 176 successfully loaded

        shared lib "dw_stl.so" version 176 successfully loaded

        shared lib "dw_gui.so" version 176 successfully loaded

        shared lib "dw_mdm.so" version 176 successfully loaded

rdisp/softcancel_sequence :  -> 0,5,-1

use internal message server connection to port 3900

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >sapmid_SID_00                           <

DpShMCreate: sizeof(wp_adm)             29512   (1736)

DpShMCreate: sizeof(tm_adm)             5941632 (29560)

DpShMCreate: sizeof(wp_ca_adm)          24064   (80)

DpShMCreate: sizeof(appc_ca_adm)        8000    (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/548056/548064

DpShMCreate: sizeof(comm_adm)           548064  (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm)          0       (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm)           0       (72)

DpShMCreate: sizeof(vmc_adm)            0       (1864)

DpShMCreate: sizeof(wall_adm)           (40056/36728/64/192)

DpShMCreate: sizeof(gw_adm)     48

DpShMCreate: SHM_DP_ADM_KEY             (addr: 0x700000000156000, size: 6637288)

DpShMCreate: allocated sys_adm at 0x700000000156000

DpShMCreate: allocated wp_adm at 0x700000000158250

DpShMCreate: allocated tm_adm_list at 0x70000000015f598

DpShMCreate: allocated tm_adm at 0x70000000015f5f8

DpShMCreate: allocated wp_ca_adm at 0x700000000709f78

DpShMCreate: allocated appc_ca_adm at 0x70000000070fd78

DpShMCreate: allocated comm_adm at 0x700000000711cb8

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 0x700000000797998

DpShMCreate: allocated gw_adm at 0x700000000797a18

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 0x700000000797a48

DpShMCreate: allocated wall_adm at 0x700000000797ab8

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpRqQInit: Parameter rdisp/queue_lock_level = 2

rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

*** WARN  Shm 51 in Pool 10     3125 KB estimated     17836 KB real (  +14711 KB

   +470 %)

<ES> client 0 initializing ....

<ES> EsILock: use spinlock for locking

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation std

<ES> Info: use normal pages (no huge table support available)

EsStdUnamFileMapInit: ES base = 0x0x700000030000000

EsStdInit: Extended Memory 4092 MB allocated

<ES> 1022 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 96 MB

J2EE server info

  start = TRUE

  state = STARTED

  pid = 14811168

  argv[0] = /usr/sap/SID/DVEBMGS00/exe/jcontrol

  argv[1] = jcontrol

  argv[2] = pf=/usr/sap/SID/SYS/profile/MID_DVEBMGS00_sapSID

  argv[3] = -DSAPSTART=1

  argv[4] = -DCONNECT_PORT=65000

  argv[5] = -DSAPSYSTEM=00

  argv[6] = -DSAPSYSTEMNAME=

  argv[7] = -DSAPMYNAME=sapmid_

  argv[8] = -DSAPPROFILE=/usr/sap/MID/SYS/profile/MID_DVEBMGS00_

  argv[9] = -DFRFC_FALLBACK=ON

  argv[10] = -DFRFC_FALLBACK_HOST=localhost

  start_lazy = 0

  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Mon Aug 20 21:04:03 2012

WLM Tag 'MID/DSP' successfully set for this process

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1706]

***LOG Q0K=> DpMsAttach, mscon ( sapmid) [dpxxdisp.c   12778]

DpStartStopMsg: send start message (myname is >sapmid_MID_00                   

       <)

DpStartStopMsg: start msg sent

CCMS: start to initalize 3.X shared alert area (first segment).

DpJ2eeLogin: j2ee state = CONNECTED

DpMsgAdmin: Set release to 7010, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1048]

DpMsgAdmin: Set patchno for this platform to 176

Release check o.K.

Mon Aug 20 21:04:12 2012

MBUF state ACTIVE

DpModState: change server state from STARTING to ACTIVE

Mon Aug 20 21:04:43 2012

J2EE server info

  start = TRUE

  state = ACTIVE

  pid = 14811168

  http = 50000

  https = 50001

  start_lazy = 0

  start_control = SAP J2EE startup framework

Mon Aug 20 21:07:23 2012

DpHdlDeadWp: restart wp (pid=4325800) automatically

Mon Aug 20 21:32:23 2012

DpHdlDeadWp: restart wp (pid=3277150) automatically

Mon Aug 20 22:32:43 2012

DpHdlDeadWp: restart wp (pid=8585238) automatically

Mon Aug 20 23:32:43 2012

DpHdlDeadWp: restart wp (pid=8388768) automatically

Tue Aug 21 00:32:43 2012

DpHdlDeadWp: restart wp (pid=8388770) automatically

Tue Aug 21 01:32:43 2012

DpHdlDeadWp: restart wp (pid=12189772) automatically

Tue Aug 21 01:46:44 2012

DpHdlDeadWp: restart wp (pid=7798926) automatically

Tue Aug 21 02:32:23 2012

DpHdlDeadWp: restart wp (pid=11010270) automatically

  Tue Aug 21 03:32:23 2012

DpHdlDeadWp: restart wp (pid=11010272) automatically

  Tue Aug 21 04:33:03 2012

DpHdlDeadWp: restart wp (pid=3146128) automatically

  Tue Aug 21 05:32:44 2012

DpHdlDeadWp: restart wp (pid=11010274) automatically

  Tue Aug 21 06:32:23 2012

DpHdlDeadWp: restart wp (pid=11010302) automatically

  Tue Aug 21 07:31:44 2012

DpHdlDeadWp: restart wp (pid=11010048) automatically

dev_server0 not generated

thanks

former_member191911
Contributor
0 Kudos

As Ratnait asked; what return code do you get in the dev_server0 when the java server is going down?

Former Member
0 Kudos

Hi ,

dev_server0, and default.trac. file not updating any thing from last 3 days

former_member191911
Contributor
0 Kudos

When checking the log, it says: DpJ2eeStart: j2ee state = STARTED

Somehow your system thinks that the j2ee engine is already started. Can you check if there is a jstart or jcontrol process active?

Kr. Mark

Former Member
0 Kudos

yes active  SIDadm  7602446 14811168   0 21:04:31      -  0:07 /usr/sap/SID/DVEBMGS00/exe/jlaunch pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS00_sapsid -DSAPINFO=SID_00_sdm -nodeId=2 -file=/usr/sap/SID/DVEBMGS00/SDM/program/config/sdm_jstartup.properties -syncSem=36700246 -nodeName=sdm -jvmOutFile=/usr/sap/SID/DVEBMGS00/work/jvm_sdm.out -stdOutFile=/usr/sap/SID/DVEBMGS00/work/std_sdm.out -locOutFile=/usr/sap/SID/DVEBMGS00/work/dev_sdm -mode=JCONTROL pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS00_sapsid -DSAPSTART=1 -DCONNECT_PORT=64999 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=SID -DSAPMYNAME=sapsid_SID_00 -DSAPPROFILE=/usr/sap/SID/SYS/profile/SID_DVEBMGS00_sapSID -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost

0:00 jcontrol pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS00_sapsid -DSAPSTART=1 -DCONNECT_PORT=65000 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=SID -DSAPMYNAME=sapSID_SID_00 -DSAPPROFILE=/usr/sap/SID/SYS/profile/SID_DVEBMGS00_sapsid -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost

former_member191911
Contributor
0 Kudos

Now I'm getting confused.. dev_server0 is not being updated, but processes are still active.

Can you check the status of the system using jcmon pf=<instance profile>

Assuming you don't get proper response when logging on to the java stack via a browser, can you execute a hard shutdown via transaction SMICM in the ABAP stack.

SMICM -> AS java -> Cluster global -> send hard shutdown - with restart.

Kr. Mark

Former Member
0 Kudos

------------------------------------------------------------

SAP System Name   : SID

SAP System        : 00

MS Host           : sapsid

MS Port           : 3901

Process Count     : 3

PID of JControl   : 9437220

State of JControl : All processes running

State inside MS   : All processes running

Admin URL         :

------------------------------------------------------------

|Idx|Name               |PID     |State                |Error|Restart|

|---|-------------------|--------|---------------------|-----|-------|

|  0|dispatcher         |11010054|Running              |    0|yes    |

|  1|server0            |       0|Initial              |    0|yes    |

|  2|SDM                | 7405746|Running              |    0|yes    |

server is initial stage, it is not starting

Former Member
0 Kudos

Hello Venkat

Are you using DDIC user in any of your configuration. Check this message from the log which you have pasted above.

[Setup]A failure occured while connecting to ABAP stack on localhost sys=00 client=001 user=DDIC

[EXCEPTION]

{0}#1#com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts

Regards

Amit Padmawar

Former Member
0 Kudos

Hi Amit,

we already updrade abap stack, i checked any user locked, no usered locked in the system , i can't able login visual admin,i restarted the server but no use, still server is in intial mode only

thanks

Former Member
0 Kudos

can you please check defaulttrace and application log. If possible attach it to the message.

Regards

Amit

former_member189725
Active Contributor
0 Kudos

Can you paste the dev_server0 and dev_disp trace files as well.

I hope this is an ABAP+JAVA system . Can you check if the license of the system is valid .

Regards

Ratnait

Former Member
0 Kudos

Hi,

as suggested above give logs from work directory.

please let me know is there any changes was done before this restart?

kernel update or any?

Thanks,

Venkat