J2EE Engine won't start after PDK Deployment
Good morning everybody,
I tried to deploy the PDK a couple of days ago. The first file (pdkcontent6090.sca I think) deployed fine in about 15 minutes, the second one (pdkjavadoc6090.sca) however didn't. It ran three hours before I stopped the deployment. There were no error messages in any of the logfiles.
Now my Server won't start. I've been looking through the logfiles and the only entry that shows anything wrong is in server.0.log:
<i>#1.5#000255AB8B3B001D00000006000009D40003F9B6E70BE132#1118
988885806#/System/Server/SLDService##com.sap.sldserv.SldServerFrame
######19f5ae40def711d9baed000255ab8b3b#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###
Communication configuration is incomplete. No data transfer possible until corrected.#</i>
Everything apart from that looks normal. I can't find any documentation on what this means or what I can do
to get everything back to running again...
Any ideas? We're on WAS 6.40 and EP6SP9.
Thanks!!
Gesche
It's not running, the page reads:
"Application stopped!
Details: You have requested an application that is currently stopped"
Similar Messages
-
J2EE engine doesn't start after changing password in configtool
The story is
1. -->I tried to deploy WebDynpro app but it throws error message:
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool.
2. --> so I changed the password through configtool. restart everything but J2EE engine doesn't up anymore (grey colour in MMC).
3. --> I'm trying to run configtool (select default) but it won't start (because j2ee engine doesn't up).
Q. --> How to start configtool? how to reset back the password? or how to rectify this Database issue? help....
note: I can login to Database in MMC.
thanks all
log from developer trace:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:60)
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.dbtech.jdbc.exceptions.DatabaseException: [-4008]: Unknown user name/password combinationHi Anthony
In the configtool (secure store) where you have changed the password there are two fields for password change (one for db and other for engine).You changed the password but your databse password is the earlier one .So first change the DB password because this is the password your instance uses to connect to DB and the same should be mentioned in the secure store of the configtool .If there is any mismatch you will face the problem which you are telling.
Any issues feel free to ask.
Reward with suitable points -
Exit Code -11114 J2EE Engine doesn't start completely. DESPERATE
XI system - Windows - Oracle - ABAP + Java Stack
We would like to upgrade our J2EE Engine Version however, during the upgrade, there is a phase wherein the J2EE Engine is being started. But, as it is being started, it returns an error and it provides the message Exit Code -11114 and it starts restarts the J2EE Instance automatically over and over again. I've read a forum here that resolved this error. However, the scenario wherein the data source is database_only is not applicable to our case since our data source is already dataSourceConfiguration_r3_roles_db.xml. Furthermore, I've read in one of the logs that indicates that: Critical shutdown was invoked. Reason is: 5 core services have timed out http://adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin. Hope you could help us out! Please help us! This is affecting the business operation since the server 0 doesn't startup completely, thus the java sites are all inaccessible.
Here is one part of the trace.
#1.5#0015C588AED40047000001690000141800044578CA30039C#1202284997468#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/com.sap.aii.af.sdk.rnif.message.listener] application.
The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/com.sap.aii.af.sdk.rnif.message.listener.
Exception id: [0015C588AED40047000001670000141800044578CA300130]#
#1.5#0015C588AED400470000016E0000141800044578CA30A0A8#1202284997515#com.sap.engine.services.servlets_jsp.Deploy##com.sap.engine.services.servlets_jsp.Deploy#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application. The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.servlets_jsp.server.container.StopAction.unBindApp(StopAction.java:92)
at com.sap.engine.services.servlets_jsp.server.container.StopAction.commitStop(StopAction.java:56)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.commitStop(WebContainer.java:419)
at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:262)
at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:305)
at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:296)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:117)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:235)
at com.sap.engine.services.deploy.server.FinishListener.run(FinishListener.java:77)
at com.sap.engine.services.deploy.server.FinishListener.makeOperation(FinishListener.java:57)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startTransactionsLocal(DeployServiceImpl.java:4183)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopMyApplications(DeployCommunicatorImpl.java:214)
at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:235)
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:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#0015C588AED40047000001700000141800044578CA30A304#1202284997515#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application.
The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
Exception id: [0015C588AED400470000016E0000141800044578CA30A0A8]#
#1.5#0015C588AED4005D0000004A0000141800044578CA38DF9E#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_5]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: java.lang.Thread | toString: Thread[SAPEngine_EnquReader,5,main]] with classloader [com.sap.engine.boot.CoreClassLoader@a981ca]#
#1.5#0015C588AED4005D0000004B0000141800044578CA38F484#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_51]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.service630.container.ServiceStopper | toString: com.sap.engine.core.service630.container.ServiceStopper@122c960] with classloader [null]#
#1.5#0015C588AED4005D0000004C0000141800044578CA38F5B3#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_71]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]d2e636] with classloader [[email protected]5b6@service:log_configurator]#
#1.5#0015C588AED40047000001780000141800044578CA38F6DB#1202284998062#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Service servlet_jsp error java.lang.ThreadDeath during shutdown.#
#1.5#0015C588AED4005D0000004D0000141800044578CA3DA356#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_2]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.jms.WorkerHandlerImpl | toString: com.sap.aii.af.service.jms.WorkerHandlerImpl@81f25] with classloader [[email protected]b87f@service:com.sap.aii.adapter.jms.svc]#
#1.5#0015C588AED4005D0000004E0000141800044578CA3DA528#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_25]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory | toString: [email protected]2222] with classloader [[email protected]74b@common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore]#
#1.5#0015C588AED4005D0000004F0000141800044578CA3DA681#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_29]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.scheduler.JobBroker$Broker | toString: com.sap.aii.af.service.scheduler.JobBroker$Broker@134d801] with classloader [[email protected]619e@service:com.sap.aii.af.svc]#
#1.5#0015C588AED4005D000000500000141800044578CA3DA79A#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_32]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.adapter.xi.ms.SLDReader | toString: com.sap.aii.adapter.xi.ms.SLDReader@513bb5] with classloader [[email protected]4ab4@service:com.sap.aii.adapter.xi.svc]#
#1.5#0015C588AED4001900000000000034D800044578FAB55C7D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<super()>#
#1.5#0015C588AED4001900000001000034D800044578FAB58D2D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
#1.5#0015C588AED4001900000002000034D800044578FAB597E9#1202285811453#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
#1.5#0015C588AED4001900000003000034D800044578FAC784C7#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
#1.5#0015C588AED4001900000004000034D800044578FAC78D1C#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
#1.5#0015C588AED4000000000016000034D8000445790BF2E967#1202286100703#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Wed Feb 06 16:21:40 CST 2008 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
Service com.sap.aii.af.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service com.sap.aii.adapter.marketplace.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service ejb > hard reference to interface security.
Service com.sap.aii.af.security.service > hard reference to service keystore.
Service ssl > hard reference to service keystore.
Service com.sap.aii.adapter.jms.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service adminadapter > hard reference to service jmx.
Service tcsecsecurestorage~service > hard reference to service keystore.
Service pmi > hard reference to service tcsecdestinations~service.
Service security > hard reference to service com.sap.security.core.ume.service.
Service jms_provider > hard reference to service security.
Service sld > hard reference to service tcsecsecurestorage~service.
Service jmx > hard reference to interface security.
Service rfcengine > hard reference to service ejb.
Service tcsecsaml~service > hard reference to service adminadapter.
Service telnet > hard reference to service shell.
Service com.sap.aii.adapter.jdbc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service tclmctcculculservice_sda > hard reference to service jmx.
Service webdynpro > hard reference to interface shell.
Service tcsecvsiservice > hard reference to service tcsecdestinationsservice.
Service tceCATTPingservice > hard reference to interface shell.
Service com.sap.aii.af.ispeak.svc > hard reference to service applocking.
Service tcsecdestinationsservice > hard reference to service tcsecsecurestorageservice.
Service dsr > hard reference to service security.
Service keystore > hard reference to service security.
Service applocking > hard reference to service security.
Service tclmctcculservice_sda > hard reference to service jmx.
Service monitor > hard reference to service jmx.
Service com.sap.security.core.ume.service > service com.sap.security.core.ume.service start method invoked.
Service com.sap.aii.adapter.bc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service com.sap.aii.adapter.rfc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service tc.monitoring.logviewer > hard reference to service jmx.
Service apptracing > hard reference to service jmx.
Service com.sap.aii.af.ms.svc > hard reference to service com.sap.aii.af.svc.
Service com.sap.aii.af.cpa.svc > hard reference to service sld.
Service shell > hard reference to interface security.
Service tcsecwssecservice > hard reference to service tcsecsecurestorageservice.
Service com.sap.aii.adapter.mail.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service servlet_jsp > hard reference to interface security.
Service com.sap.aii.adapter.file.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service classload > hard reference to service security.
Service basicadmin > hard reference to service jmx.
Service com.sap.aii.adapter.xi.svc > hard reference to service com.sap.aii.af.cpa.svc.
#1.5#0015C588AED4000000000018000034D8000445790BF36AF2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###43 services have timed out.#
#1.5#0015C588AED400000000001A000034D8000445790BF36CBF#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000001C000034D8000445790BF36E70#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.marketplace.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000001E000034D8000445790BF3702D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ejb has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000020000034D8000445790BF371D8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.security.service has timed out > hard reference to service keystore.#
#1.5#0015C588AED4000000000022000034D8000445790BF3737F#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ssl has timed out > hard reference to service keystore.#
#1.5#0015C588AED4000000000024000034D8000445790BF3752A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000026000034D8000445790BF376D2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service adminadapter has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000028000034D8000445790BF3787A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsecurestorage~service has timed out > hard reference to service keystore.#
#1.5#0015C588AED400000000002A000034D8000445790BF37ACC#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service pmi has timed out > hard reference to service tcsecdestinations~service.#
#1.5#0015C588AED400000000002C000034D8000445790BF37D4C#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service security has timed out > hard reference to service com.sap.security.core.ume.service.#
#1.5#0015C588AED400000000002E000034D8000445790BF37EF7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jms_provider has timed out > hard reference to service security.#
#1.5#0015C588AED4000000000030000034D8000445790BF380A1#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service sld has timed out > hard reference to service tcsecsecurestorage~service.#
#1.5#0015C588AED4000000000032000034D8000445790BF3824E#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jmx has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000034000034D8000445790BF383F8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service rfcengine has timed out > hard reference to service ejb.#
#1.5#0015C588AED4000000000036000034D8000445790BF385A7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsaml~service has timed out > hard reference to service adminadapter.#
#1.5#0015C588AED4000000000038000034D8000445790BF38754#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service telnet has timed out > hard reference to service shell.#
#1.5#0015C588AED400000000003A000034D8000445790BF38903#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jdbc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000003C000034D8000445790BF38AB4#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculculservice_sda has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000003E000034D8000445790BF38C5D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service webdynpro has timed out > hard reference to interface shell.#
#1.5#0015C588AED4000000000040000034D8000445790BF38E07#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecvsiservice has timed out > hard reference to service tcsecdestinationsservice.#
#1.5#0015C588AED4000000000042000034D8000445790BF38FD6#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tceCATTPingservice has timed out > hard reference to interface shell.#
#1.5#0015C588AED4000000000044000034D8000445790BF3918B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ispeak.svc has timed out > hard reference to service applocking.#
#1.5#0015C588AED4000000000046000034D8000445790BF3938A#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecdestinationsservice has timed out > hard reference to service tcsecsecurestorageservice.#
#1.5#0015C588AED4000000000048000034D8000445790BF3953F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service dsr has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004A000034D8000445790BF396EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service keystore has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004C000034D8000445790BF398A2#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service applocking has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004E000034D8000445790BF39B53#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculservice_sda has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000050000034D8000445790BF39CFE#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service monitor has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000052000034D8000445790BF39EAB#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.security.core.ume.service has timed out > service com.sap.security.core.ume.service start method invoked.#
#1.5#0015C588AED4000000000054000034D8000445790BF3A068#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.bc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000056000034D8000445790BF3A217#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.rfc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000058000034D8000445790BF3A3CD#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tc.monitoring.logviewer has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000005A000034D8000445790BF3A5EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service apptracing has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000005C000034D8000445790BF3A7B3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ms.svc has timed out > hard reference to service com.sap.aii.af.svc.#
#1.5#0015C588AED400000000005E000034D8000445790BF3A967#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.cpa.svc has timed out > hard reference to service sld.#
#1.5#0015C588AED4000000000060000034D8000445790BF3AB0C#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service shell has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000062000034D8000445790BF3ACBC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecwssecservice has timed out > hard reference to service tcsecsecurestorageservice.#
#1.5#0015C588AED4000000000064000034D8000445790BF3AE81#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.mail.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000066000034D8000445790BF3B03B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service servlet_jsp has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000068000034D8000445790BF3B2D1#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.file.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000006A000034D8000445790BF3B47F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service classload has timed out > hard reference to service security.#
#1.5#0015C588AED400000000006C000034D8000445790BF3B628#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service basicadmin has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000006E000034D8000445790BF3B7D3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.xi.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000070000034D8000445790BF3BA67#1202286100750#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: 5 core services have timed out [adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin].#Hello Sir,
I am also having the similar prblem after upgrading the AIX 5.3 TL 5 to TL6.
I would really like to know what you did to solve you problem, even though our scenario is a little different. -
Hi All.
I installed a Dialog instance.
After the installation of the license key on the central instance, the dialog J2EE Engine does not start anymore.
Here it is the std_server0.out log:
stdout/stderr redirect
node name : server0
pid : 1298548
system name : PRP
system nr. : 10
started at : Mon Sep 3 19:07:54 2007
[Thr 1] Mon Sep 3 19:07:55 2007
[Thr 1] MtxInit: -2 0 0
JVMST080: verbosegc is enabled
JVMST082: -verbose:gc output will be written to stderr
^MSAP J2EE Engine Version 7.00 PatchLevel is starting...
^M
Loading: LogManager ... 1887 ms.
Loading: PoolManager ... 3 ms.
Loading: ApplicationThreadManager ... 452 ms.
Loading: ThreadManager ... 428 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 392 ms.
Loading: LockingManager ... 140 ms.
Loading: ConfigurationManager ... 4656 ms.
Loading: LicensingManager ... 28 ms.
Loading: CacheManager ... 311 ms.
Loading: ServiceManager ...
<AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>
<AF[1]: managing allocation failure, action=0 (959472304/1073740288)>
<GC(1): GC cycle started Mon Sep 3 19:08:13 2007
<GC(1): freed 64170704 bytes, 95% free (1023643008/1073740288), in 136 ms>
<GC(1): mark: 123 ms, sweep: 13 ms, compact: 0 ms>
<GC(1): refs: soft 0 (age >= 32), weak 0, final 475, phantom 0>
<AF[1]: completed in 159 ms>
Loading services.:
Service cross started. (72 ms).
Service file started. (156 ms).
Service memory started. (160 ms).
Service userstore started. (24 ms).
Service timeout started. (51 ms).
Service runtimeinfo started. (8 ms).
Service trex.service started. (90 ms).
Service jmx_notification started. (77 ms).
Service p4 started. (182 ms).
Service classpath_resolver started. (99 ms).
Service deploy started. (9491 ms).
Service MigrationService started. (28 ms).
Service bimmrdeployer started. (6 ms).
Service log_configurator started. (21621 ms).
Service locking started. (3 ms).
Service http started. (772 ms).
Service naming started. (1518 ms).
Service failover started. (23 ms).
Service appclient started. (29 ms).
Service javamail started. (87 ms).
Service ts started. (70 ms).
Service jmsconnector started. (80 ms).
Service licensing started. (10 ms).
Service iiop started. (141 ms).
Service connector started. (119 ms).
Service configuration started. (31 ms).
Service webservices started. (463 ms).
Service dbpool started. (8765 ms).
Sep 3, 2007 6:08:47 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME
persistence adapter "PRIVATE_DATASOURCE" failed.
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=FALSE
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
... 6 more
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=FALSE
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 3, 2007 6:08:47 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was
invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Anyone can help?
Thanks,
MarcoHi all,
after some corrections, now the problem is changed.
Here you can find the std_server0.out:
<b>com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=SAPPRP-DB SYSNR=10 GWHOST=SAPPRP-DB GWSERV=sapgw10 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'SAPPRP-DB:sapgw10' not reached
TIME Fri Sep 7 15:01:11 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 79
ERRNO TEXT A remote host refused an attempted connect operation.
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 7, 2007 2:01:11 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_55] Fatal: Critical shutdown was
invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.</b>
Thanks all,
Marco -
Com.sap.security.core.ume.service failed. J2EE Engine cannot be started
Hi,
I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
The following is the part of log file.
#1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
#1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
Please help me to solve the issue.
Thanks,
Ajay.Hi Tim,
I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps as per below URL
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jun 25, 2010 3:05:24 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
Thanks,
Ajay. -
Hi Experts,
our J2EE Engine is not starting. After application restart in SAP MMC's process list for disp+work.exe the status is yellow (Running, Message Server connectionok, ...., J2EE: Some processes running). In the J2EE Process table the server0 is stopped. He tries to start it a couple of times, but after all it stopps with exitcode -11113. So I've checked the dev_trace, the entry was:
[Thr 2376] Wed Nov 17 15:41:35 2010
[Thr 2376] *** WARNING => INFO: Unknown property [instance.box.number=EI3DVEBMGS00chopin] [jstartxx.c 841]
[Thr 2376] *** WARNING => INFO: Unknown property [instance.en.host=chopin] [jstartxx.c 841]
[Thr 2376] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 2376] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
[Thr 1128] Wed Nov 17 15:45:06 2010
[Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1128] JLaunchISetClusterId: set cluster id 2121050
[Thr 1128] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1128] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5284] Wed Nov 17 15:45:34 2010
[Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 5900] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 5900] **********************************************************************
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 5900] JLaunchCloseProgram: good bye (exitcode = -11113)
So I searched a little and found this [Thread|Restart of J2EE Engine] and modified the Heapsize. As our Server is a 32-bit machine I used this sizes:
Max heap size: 1024M
-Xms1024M // old size: 512
-XX:PermSize=512M // old size: 128
-XX:MaxPermSize=512M // old size: 128
-XX:NewSize=320M // old size: 86
-XX:MaxNewSize=320M // old size: 86
The result was another error message in dev_trace:
Error occurred during initialization of VM
Could not reserve enough space for object heap
[Thr 2396] JLaunchIAbortJava: abort hook is called
[Thr 2396] **********************************************************************
ERROR => The Java VM aborted unexpectedly.
Please see SAP Note 943602 , section 'Java VM crashes'
for additional information and trouble shooting.
[Thr 2396] JLaunchCloseProgram: good bye (exitcode = -2)
ok, so I changed the sizes again to:
Max heao size: 1024M
-XX:MaxPermSize=128M
-XX:PermSize=512M
-Xms512M
-XX:NewSize=320M
-XX:MaxNewSize=86M
But there's still the same error occurring.
Please, does someone has an idea how to solve this issue?
Thanks in advance,
TanHi Desiree,
thank you for your posting. It's getting better, but it's still not running. I've set up the same password in client 001 and in the java ume and restarted the cluster. When starting the server0 is J2EE Process Table is starting framework, then starting apps, but after something about 9 minutes its restarting, but it seems not to have errors (in the J2EE Process Table there are restarts displayed but no errors. So its better than before where the server0 restarts after 30 seconds and stopps restarting after 3 errors and 4 restarts.
But nows he's restarting and restarting....
In TA SMICM there is the J2EE server operational TRUE which was not before. When checking the RFC Destination there comes the status "not ready" during Starting framework phase and status "Service unavailable" during starting apps phase.
Here are some parts of the dev_trave:
"VM Thread" prio=5 tid=0x003cec80 nid=0x1028 runnable
"Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x7e0 runnable
[Thr 4136] JLaunchIExitJava: exit hook is called (rc = 666)
[Thr 4136] **********************************************************************
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 4136] JLaunchCloseProgram: good bye (exitcode = 666)
"VM Thread" prio=5 tid=0x003cec80 nid=0xb50 runnable
"VM Periodic Task Thread" prio=10 tid=0x011dcc88 nid=0x9e4 waiting on condition
"Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x748 runnable
[Thr 2896] Thu Nov 18 09:13:33 2010
[Thr 2896] JLaunchIExitJava: exit hook is called (rc = 666)
[Thr 2896] **********************************************************************
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 2896] JLaunchCloseProgram: good bye (exitcode = 666)
... and so on.
I'm not sure whether I should change or add entries in the configtool.bat like in your link recommended. The Engine was running with this settings before..... -
Hi All,
My j2ee engine is not starting. Kindly assist me regarding this. Kindly find below log.
Where to check this user.
stdout/stderr redirect
node name : server0
pid : 229540
system name : GSQ
system nr. : 02
started at : Tue Feb 21 18:21:43 2012
SAP J2EE Engine Version 7.00 PatchLevel 66803.450 is starting...
Loading: LogManager ... 623 ms.
Loading: PoolManager ... 2 ms.
Loading: ApplicationThreadManager ... 3568 ms.
Loading: ThreadManager ... 28 ms.
Loading: IpVerificationManager ... 12 ms.
Loading: ClassLoaderManager ... 20 ms.
Loading: ClusterManager ... 307 ms.
Loading: LockingManager ... 84 ms.
Loading: ConfigurationManager ... 1674 ms.
Loading: LicensingManager ... 19 ms.
Loading: CacheManager ... 127 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (37 ms).
Service memory started. (62 ms).
Service cafeuodi~mnuacc started. (2 ms).
Service cross started. (138 ms).
Service file started. (139 ms).
Service timeout started. (147 ms).
Service runtimeinfo started. (91 ms).
Service trex.service started. (170 ms).
Service cafeucc~api started. (196 ms).
Service userstore started. (20 ms).
Service jmx_notification started. (36 ms).
Service p4 started. (215 ms).
Service classpath_resolver started. (49 ms).
<af type="nursery" id="1" timestamp="Feb 21 18:23:25 2012" intervalms="0.000">
<minimum requested_bytes="96" />
<time exclusiveaccessms="0.209" />
<nursery freebytes="0" totalbytes="209715200" percent="0" />
<tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
<soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<gc type="scavenger" id="1" totalid="1" intervalms="0.000">
<flipped objectcount="283441" bytes="21271320" />
<tenured objectcount="0" bytes="0" />
<refs_cleared soft="685" weak="1" phantom="0" />
<finalization objectsqueued="1462" />
<scavenger tiltratio="50" />
<nursery freebytes="188305568" totalbytes="209715200" percent="89" tenureage="10" />
<tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
<soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="101.150" />
</gc>
<nursery freebytes="188303520" totalbytes="209715200" percent="89" />
<tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
<soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="102.710" />
</af>
<af type="nursery" id="2" timestamp="Feb 21 18:23:28 2012" intervalms="3381.768">
<minimum requested_bytes="32552" />
<time exclusiveaccessms="0.203" />
<nursery freebytes="16072" totalbytes="209715200" percent="0" />
<tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
<soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<gc type="scavenger" id="2" totalid="2" intervalms="3383.004">
<flipped objectcount="405653" bytes="30029056" />
<tenured objectcount="0" bytes="0" />
<refs_cleared soft="983" weak="0" phantom="0" />
<finalization objectsqueued="901" />
<scavenger tiltratio="50" />
<nursery freebytes="179257688" totalbytes="209715200" percent="85" tenureage="10" />
<tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
<soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="56.165" />
</gc>
<nursery freebytes="179225136" totalbytes="209715200" percent="85" />
<tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
<soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="57.048" />
</af>
Service log_configurator started. (8042 ms).
Service locking started. (9 ms).
Service http started. (283 ms).
<af type="nursery" id="3" timestamp="Feb 21 18:23:31 2012" intervalms="2407.476">
<minimum requested_bytes="1208" />
<time exclusiveaccessms="0.309" />
<nursery freebytes="0" totalbytes="209715200" percent="0" />
<tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
<soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<gc type="scavenger" id="3" totalid="3" intervalms="2408.194">
<flipped objectcount="554169" bytes="41224280" />
<tenured objectcount="0" bytes="0" />
<refs_cleared soft="952" weak="0" phantom="0" />
<finalization objectsqueued="1316" />
<scavenger tiltratio="50" />
<nursery freebytes="167984600" totalbytes="209715200" percent="80" tenureage="10" />
<tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
<soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="76.821" />
</gc>
<nursery freebytes="167983392" totalbytes="209715200" percent="80" />
<tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
<soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="78.249" />
</af>
Service naming started. (801 ms).
Service failover started. (69 ms).
Service javamail started. (207 ms).
Service ts started. (173 ms).
Service appclient started. (192 ms).
Service licensing started. (47 ms).
Service jmsconnector started. (308 ms).
Service connector started. (280 ms).
Service iiop started. (325 ms).
Service webservices started. (749 ms).
<af type="nursery" id="4" timestamp="Feb 21 18:23:33 2012" intervalms="2262.903">
<minimum requested_bytes="32" />
<time exclusiveaccessms="0.192" />
<nursery freebytes="0" totalbytes="209715200" percent="0" />
<tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
<soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<gc type="scavenger" id="4" totalid="4" intervalms="2264.002">
<flipped objectcount="614335" bytes="45869976" />
<tenured objectcount="0" bytes="0" />
<refs_cleared soft="35" weak="0" phantom="0" />
<finalization objectsqueued="7" />
<scavenger tiltratio="50" />
<nursery freebytes="163275192" totalbytes="209715200" percent="77" tenureage="10" />
<tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
<soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="78.029" />
</gc>
<nursery freebytes="163273144" totalbytes="209715200" percent="77" />
<tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
<soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
<loa freebytes="86402048" totalbytes="86402048" percent="100" />
</tenured>
<time totalms="79.277" />
</af>
Service deploy started. (10986 ms).
Service com.sap.portal.runtime.config.kmreadonly started. (11 ms).
Service configuration started. (39 ms).
Service MigrationService started. (69 ms).
Service bimmrdeployer started. (17 ms).
Service dbpool started. (1237 ms).
Service UT started. (14 ms).
Service cafeugpmailcf started. (53 ms).
Feb 21, 2012 6:23:37 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Password logon no longer possible - too many failed attempts". This message is critical if it appears during the startup of the AS Java.
Feb 21, 2012 6:23:37 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_78] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
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:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
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:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Feb 21, 2012 6:23:37 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_78] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
</verbosegc>I would recommand to login as <SID>adm to your central instance and go to path usr\sap\<systemid>\<system instance>\J2EE\configtool
then configtool.bat and start it.
also access this tool only to make password reset
Refer thread[http://forums.sdn.sap.com/thread.jspa?threadID=2107011&tstart=15] for setting env variable
Regards,
Edited by: Rupali B on Feb 22, 2012 2:09 PM -
J2EE Engine cannot be started. SAP CRM EHP1 Dialog Instance Installation
Hi All,
During Installation of a DI on a Linux host, I encounterd a problem. An error occured during " start dialog instance". The ABAP enginee is started successfully where as the JAVA Enginee cant be started. During investigation I found from the log directory
..j2ee/cluster/server0/log as stated below ..
#1.#0050569F663E001E0000000C0000054F0004803004D18B3F#1266843634469#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_64##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=false
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
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:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=false
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
#1.#0050569F663E001E0000000E0000054F0004803004D18C49#1266843634469#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_64##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
I checked with the env variable and parameter, it all looks good. If anybody finds the same issue please suggest ....
Thanks in Advance.
Regards,
ShashiThere is a troubleshooting topic for this on the Help Portal.
See http://help.sap.com/saphelp_nw70ehp1/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm.
-Michael -
J2EE engine not getting started
Hi All,
My J2ee engine isnt getting started. When i check the logs, i see the following error,
Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect
Loading: LogManager ... 672 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 78 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 218 ms.
Loading: LockingManager ... 94 ms.
Loading: ConfigurationManager ...
Loading: ConfigurationManager returned false!
Kernel not loaded. System halted.
Can anybody help me out with this ??
Thanks in advance,
PranavHi Arun,
ya indeed it looks like a DB connection problem. When i check the logs i see the following error :
#1.5#001321D5DC2000000000001500049EDC0004163FAB8F0C2D#1150362623876#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Error while connecting to DB.
=======================================================
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at</i></i> com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerFactoryImpl.<init>(ConfigurationHandlerFactoryImpl.java:30)
at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:189)
at com.sap.engine.core.configuration.AbstractConfigurationManagerImpl.init(AbstractConfigurationManagerImpl.java:169)
at com.sap.engine.core.Framework.loadSingleManager(Framework.java:560)
at com.sap.engine.core.Framework.loadManagers(Framework.java:254)
at com.sap.engine.core.Framework.start(Framework.java:188)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: [SAP_NWMss][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPBQ3DB'. The user is not associated with a trusted SQL Server connection.
at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:579)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
Actually i've upgraded my SQL Server2000 DB to SQL Server 2005, i suspect that causes the problem. Would be great if somebody can provide me any further clues..
Regards,
Pranav -
Firefox won't start after downloading update. I've reinstalled Firefox, still won't start. Help says check virtualization settings. What and where are virtualization settings? I have Windows XP.
This might be Zone Alarm since it provides virtualization. Please try the instructions to turn off virtualization in the following support question
http://support.mozilla.com/en-US/questions/880170 -
IPhoto won't start after upgrade 1.1 for my new iMac. Now what do I do?
Had to upgrade according to screen. iPhoto won't start after upgrade 1.1 for my new iMac. Now what do I do?
I have restarted the computer. Brand new iMac intel. v 10.9.4You need to upgrade iPhoto for Mavericks. Download the upgrade using App Store.
-
C3-01 won't start after charging
I'm so angry right now but I will try and be cool about this!
I bought C3-01 mobile phone about four months ago and it is already causing me problems.
The mobile phone simply won’t start after charging. Last time i charged it, it miraculously came to life only, and only after annoying me for about hour and a half. Now I fear it is completely dead!
Battery was not completely empty so the phone should still start even if the wall socket is broken. Which is not, wall socket works perfectly.
Nothing helps! I tried removing the battery and then restart. Removing the battery then removing the sim card, memory card and that piece of “advanced technology” simply won’t start!
I didn’t buy my new phone so that I can use my old Motorola mobile, which btw., still works after 4 years of intense usage.
I will never buy Nokia again!Hi,
Sorry to hear that your phone is not starting after charging.
I would suggest one more thing, which maybe helps. If you have another battery, please try.
If not, i would recommend to visit Nokia Care Point in your area.
To find your nearest Nokia Care Point, visit http://www.nokia.com/support and select the Repair page.
Br
Mahayv -
Hi experts.
J2EE engine will not start. Below is the lower section of the trace. I'd appreciate help with interpretation as I am a NW newby.
I just installed an J2EE key in tcode SLICENSE for our developer's subscription NW 7.0 instance. Another thread implied installing the J2EE key in visual administrator, but how is that possible if the J2EE engine is not running? I cannot establish a connection.
Thanks,
Aron
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1633]
***LOG Q0K=> DpMsAttach, mscon ( S-SAPDEV01) [dpxxdisp.c 11822]
DpStartStopMsg: send start message (myname is >S-SAPDEV01_DS1_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
Tue Jul 08 13:43:35 2008
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 146
Release check o.K.
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:43:37 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 236
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4027) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5508)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
MBUF state ACTIVE
Tue Jul 08 13:43:38 2008
DpModState: change server state from STARTING to ACTIVE
Tue Jul 08 13:44:14 2008
J2EE server info
start = TRUE
state = STARTED
pid = 3412
argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64998
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=DS1
argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:17 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 668
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4095) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3412)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Jul 08 13:44:34 2008
J2EE server info
start = TRUE
state = STARTED
pid = 5156
argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64997
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=DS1
argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:37 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 208
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4105) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5156)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Tue Jul 08 13:44:54 2008
J2EE server info
start = TRUE
state = STARTED
pid = 6072
argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64996
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=DS1
argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Tue Jul 08 13:44:57 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 200
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4117) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6072)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWNActually it was to remove compression, not to allow archiving. Sorry!
We're using Windows Server 2003. Right-click on a folder or file, choose Properties. Click on the Advanced button on the General tab. Remove the check box for Compress to save disk space, click ok. When you click on Apply there will be a prompt to apply just to that folder only or on subfolders and files as well.
When compression is applied, the text for the folder turns blue. When is not applied, the text is black. -
Mac Mini won't start after installing OS X 10.6.3
My Mac Mini won't start after installing Mac OS X Snow Leopard 10.6.3. When I turn it on, the Apple logo appears and the initialization line starts to fill, but it suddenly stops. It does that again and stops at the same point, but this time it shuts down. What should I do?
If you are coming from 10.5.8, hopefully you backed up your important data first. Your mini will need at minimum, 1 GB of RAM to install Snow Leopard and at least 5 GB of storage remaining on your boot drive.
I treat 10.6.3 as a fresh, full install over a 10.5.8 system. That means I choose Disk Utility from the Installer's menu and repartition the boot drive as a single partition, Mac OS X Extended (Journaled) format, and use the GUID partition scheme from the options button. At this point, while still in Disk Utility, I would verify the drive under First Aid.
Then I turn the installer loose, and reboot into a working 10.6.3 system, ready for the software updates that take the machine to 10.6.8.
So, following the above guidelines, reinstall 10.6.3. -
HI I have a problem with my Firefox, recently my fire fox won't start after I click on its Icon
HI I have a problem with my Firefox, recently my fire fox won't start after I click on its Icon, when I see the process in task manager Firefox is there but after a second it will end processing automatically, I have tried ff7 and ff6 and have the same problem, even re installing the Firefox doesn't fix the problem, any one know the reason? I'm using a win7 64bit, and bitdefender internet security
Hi All,
This is not a virus . I used this website & I found it very useful & you can remove it through the following steps.ar.hao123.com 1- Then right-clicking on the icon Mozilla Firefox on the desktop, then choose "Properties", as shown in the picture: 2- Select Tab "shortcut", and then delete the text after. Exe in "target" as shown in the following picture, then press "Ok" 3- Open Firefox, and then choose "options" from the list of "tools" 4- Select the tab "general", and in the list "when Firefox starts" then select "show my homepage" and in the box "homepage" then enter any other link and then press "OK"
you can visit [http://ar.hao123.com/report/ar-feedback.html Hao123] hao123
ar.hao123.com
Maybe you are looking for
-
SPED Contábil / Fiscal e NF-e. Quais pontos a SAP atenderá?
Senhores, Eu tenho uma lista do que mais ou menos seremos obrigados a ver no futuro, diante das obrigações que o governo está solicitando. Gostaria de saber sobre quais pontos abaixo a SAP tem planos de atender: 1. Relacionados ao SPED Contábil: 1.
-
My pc automatically update Mozilla, and today after the update, it restarted as always, but now I can no longer read my email, do my banking or access any secure sites.. I can open their pages, but take no action. It still work with Explorer, so it i
-
New GL - Doc Splitting - Profit Center not hitting the Zero Balance GL
Dear SAP New GL Gurus, I am trying to activate the doc splitting where the system uses a GL Account to ensure that Profit Center wise Trial Balances are tallied. I have done the following configuration till now, and I feel that these steps should ide
-
Hi, I have a 5530 XpressMusic phone with around 4000+ text messages saved on the memory card. Whenever the number of text messages increases above approximately 3500+ messages, the new text message alert stops appearing, no tone or vibration alerts.
-
I highlight and study e pubs in ibooks. Now with the up date the color highlighters that I've be using are too dark and no way to adjust opaqueness. (YOU SHOULD ADD THIS.) Is the an app to by to add to ibooks???? Or an app to but to have other highli