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.
Similar Messages
-
Error while starting J2EE Engine:com.sap.security.core.persistence.datasour
I would like to ask for your help to look into the problem being encountered in starting J2EE Engine
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
At first we identified that the user EPQASCONNECT was not created in R3 QAS system, we have created this one. At the same time, we have changed the ume.r3.connection.master.passwd to reflect the password set in R3 QAS. But still it is not working.
Also, checking the trace file for server0, the rc code is -11113.
The following users SAPJSF,J2EE_GUEST and J2EE_admin were not locked.
Followed the http://help.sap.com/saphelp_nw70/helpdata/EN/45/1bbdccc7850064e10000000a1553f7/frameset.htm. link to make changes.
The problem raised after the system refresh in QAS system. License was also installed after System refresh.
ERROR:
stdout/stderr redirect
node name : server0
pid : 5088
system name : EQ7
system nr. : 03
started at : Tue Nov 25 17:24:12 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 5444] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00 PatchLevel is starting...
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 ... 1078 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 94 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 390 ms.
Loading: LockingManager ... 125 ms.
Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87039K->2386K(130560K), 0.0150914 secs] 87039K->2386K(1005056K), 0.0152223 secs]
4969 ms.
Loading: LicensingManager ... 47 ms.
Loading: CacheManager ... 359 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service memory started. (47 ms).
Service cross started. (47 ms).
Service file started. (156 ms).
Service timeout started. (109 ms).
Service runtimeinfo started. (15 ms).
Service trex.service started. (94 ms).
Service cafeucc~api started. (141 ms).
Service userstore started. (47 ms).
Service jmx_notification started. (47 ms).
Service p4 started. (297 ms).
Service classpath_resolver started. (31 ms).
9.789: [GC 9.789: [ParNew: 89426K->9626K(130560K), 0.0389830 secs] 89426K->9626K(1005056K), 0.0390998 secs]
Service log_configurator started. (5797 ms).
Service locking started. (16 ms).
Service http started. (328 ms).
Service naming started. (469 ms).
Service failover started. (141 ms).
Service appclient started. (188 ms).
Service ts started. (235 ms).
Service javamail started. (250 ms).
Service licensing started. (0 ms).
Service jmsconnector started. (312 ms).
Service connector started. (391 ms).
Service iiop started. (312 ms).
Service webservices started. (766 ms).
19.167: [GC 19.167: [ParNew: 96666K->19159K(130560K), 0.0812264 secs] 96666K->19159K(1005056K), 0.0813454 secs]
Service deploy started. (15422 ms).
Service MigrationService started. (47 ms).
Service configuration started. (62 ms).
Service bimmrdeployer started. (31 ms).
24.849: [GC 24.849: [ParNew: 106199K->17756K(130560K), 0.0546511 secs] 106199K->17756K(1005056K), 0.0547691 secs]
Service dbpool started. (2688 ms).
Service cafeugpmailcf started. (62 ms).
Nov 25, 2008 5:24:47 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=01
client=888
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=R3DEVSER
Nov 25, 2008 5:24:47 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: Initialization of UME persistence adapter "R3_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 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:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
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:338)
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:259)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
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:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
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:338)
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:259)
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.
Nov 25, 2008 5:24:47 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_70] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
stdout/stderr redirect
node name : server0
pid : 5088
system name : EQ7
system nr. : 03
started at : Tue Nov 25 17:24:52 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4672] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00 PatchLevel is starting...
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 ... 93 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 234 ms.
Loading: LockingManager ... 110 ms.
Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87040K->2403K(130560K), 0.0136260 secs] 87040K->2403K(1005056K), 0.0137788 secs]
3203 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 203 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service memory started. (47 ms).
Service cross started. (32 ms).
Service file started. (47 ms).
Service timeout started. (63 ms).
Service runtimeinfo started. (0 ms).
Service trex.service started. (63 ms).
Service cafeucc~api started. (203 ms).
Service p4 started. (328 ms).
Service jmx_notification started. (78 ms).
Service userstore started. (78 ms).
Service classpath_resolver started. (46 ms).
6.865: [GC 6.865: [ParNew: 89443K->9702K(130560K), 0.0411006 secs] 89443K->9702K(1005056K), 0.0412578 secs]
Service log_configurator started. (6141 ms).
Service locking started. (0 ms).
Service naming started. (484 ms).
Service failover started. (172 ms).
Service appclient started. (219 ms).
Service http started. (813 ms).
Service jmsconnector started. (422 ms).
Service ts started. (422 ms).
Service javamail started. (469 ms).
Service connector started. (453 ms).
Service licensing started. (110 ms).
Service iiop started. (313 ms).
Service webservices started. (1063 ms).
16.407: [GC 16.407: [ParNew: 96742K->19088K(130560K), 0.0834244 secs] 96742K->19088K(1005056K), 0.0835901 secs]
Service deploy started. (15859 ms).
Service MigrationService started. (47 ms).
Service configuration started. (47 ms).
Service bimmrdeployer started. (16 ms).
22.173: [GC 22.173: [ParNew: 106113K->17739K(130560K), 0.0551702 secs] 106113K->17739K(1005056K), 0.0553234 secs]
Service dbpool started. (2625 ms).
Service cafeugpmailcf started. (78 ms).
Nov 25, 2008 5:25:22 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=01
client=888
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=R3DEVSER
Nov 25, 2008 5:25:22 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "R3_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 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:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
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:338)
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:259)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
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:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
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:338)
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:259)
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.
Nov 25, 2008 5:25:22 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_62] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
stdout/stderr redirect
node name : server0
pid : 5088
system name : EQ7
system nr. : 03
started at : Tue Nov 25 17:25:27 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 9304] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00 PatchLevel is starting...
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 ... 656 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 94 ms.
Loading: ThreadManager ... 15 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 219 ms.
Loading: LockingManager ... 94 ms.
Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87040K->2414K(130560K), 0.0145828 secs] 87040K->2414K(1005056K), 0.0147378 secs]
3015 ms.
Loading: LicensingManager ... 47 ms.
Loading: CacheManager ... 172 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service memory started. (47 ms).
Service cross started. (31 ms).
Service file started. (63 ms).
Service timeout started. (46 ms).
Service runtimeinfo started. (16 ms).
Service trex.service started. (78 ms).
Service cafeucc~api started. (156 ms).
Service p4 started. (282 ms).
Service classpath_resolver started. (32 ms).
Service userstore started. (15 ms).
Service jmx_notification started. (47 ms).
6.784: [GC 6.784: [ParNew: 89454K->9721K(130560K), 0.0417499 secs] 89454K->9721K(1005056K), 0.0419073 secs]
Service log_configurator started. (5266 ms).
Service locking started. (0 ms).
Service http started. (406 ms).
Service naming started. (469 ms).
Service failover started. (94 ms).
Service javamail started. (250 ms).
Service ts started. (235 ms).
Service appclient started. (250 ms).
Service licensing started. (31 ms).
Service jmsconnector started. (329 ms).
Service connector started. (406 ms).
Service iiop started. (312 ms).
Service webservices started. (688 ms).
16.028: [GC 16.028: [ParNew: 96761K->19104K(130560K), 0.0751680 secs] 96761K->19104K(1005056K), 0.0753377 secs]
Service deploy started. (15438 ms).
Service MigrationService started. (47 ms).
Service bimmrdeployer started. (16 ms).
Service configuration started. (62 ms).
21.840: [GC 21.840: [ParNew: 106140K->17748K(130560K), 0.0443068 secs] 106140K->17748K(1005056K), 0.0444546 secs]
Service dbpool started. (2656 ms).
Service cafeugpmailcf started. (78 ms).
Nov 25, 2008 5:25:57 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=01
client=888
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=R3DEVSER
Nov 25, 2008 5:25:57 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: Initialization of UME persistence adapter "R3_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 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:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
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:338)
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:259)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
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:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)
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:338)
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:259)
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.
Nov 25, 2008 5:25:57 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_63] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
stdout/stderr redirect
node name : server0
pid : 5088
system name : EQ7
system nr. : 03
started at : Tue Nov 25 17:25:58 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 8240] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00 PatchLevel is starting...
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 ... 656 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 94 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 15 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 266 ms.
Loading: LockingManager ... 79 ms.
Loading: ConfigurationManager ... 0.000: [GC 0.000: [ParNew: 87039K->2718K(130560K), 0.0175167 secs] 87039K->2718K(1005056K), 0.0176768 secs]
4250 ms.
Loading: LicensingManager ... 46 ms.
Loading: CacheManager ... 250 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (15 ms).
service telnet ================= ERROR =================
Service memory started. (31 ms).
Service cross started. (32 ms).
Service file started. (63 ms).
7.854: [GC 7.855: [ParNew: 89758K->7739K(130560K), 0.0387127 secs] 89758K->7739K(1005056K), 0.0388651 secs]
Service timeout started. (94 ms).
Service runtimeinfo started. (15 ms).
Service cafeucc~api started. (141 ms).
Service trex.service started. (141 ms).
Service userstore started. (79 ms).
Service jmx_notification started. (47 ms).
Service p4 started. (375 ms).
Service classpath_resolver started. (47 ms).
Service log_configurator started. (6343 ms).
Service locking started. (0 ms).
Service naming started. (641 ms).
Service failover started. (172 ms).
Service ts started. (281 ms).
Service appclient started. (187 ms).
Service javamail started. (312 ms).
Service licensing started. (31 ms).
Service jmsconnector started. (297 ms).
Service http started. (1000 ms).
Service connector started. (453 ms).
Service iiop started. (281 ms).
Service webservices started. (906 ms).
16.628: [GC 16.628: [ParNew: 94779K->15719K(130560K), 0.0715624 secs] 94779K->15719K(1005056K), 0.0717470 secs]
23.824: [GC 23.824: [ParNew: 102759K->17568K(130560K), 0.0594877 secs] 102759K->17568K(1005056K), 0.0596196 secs]
Service deploy started. (21469 ms).
Service configuration started. (47 ms).
Service bimmrdeployer started. (15 ms).
Service MigrationService started. (78 ms).
Service dbpool started. (3641 ms).
33.638: [GC 33.638: [ParNew: 104608K->20954K(130560K), 0.0721131 secs] 104608K->20954K(1005056K), 0.0722444 secs]
Service cafeugpmailcf started. (156 ms).
Nov 25, 2008 5:26:38 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect (repeat logon)". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=01
client=888
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=R3DEVSER
Nov 25, 2008 5:26:38 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: Initialization of UME persistence adapter "R3_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 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: Name or password is incorrect (repeat logon)
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:338)
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:259)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
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: Name or password is incorrect (repeat logon)
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:338)
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:259)
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.
Nov 25, 2008 5:26:38 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_71] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Regards,
RamanaHi Friends,
Issue got resolved.. Sorry for delay reply.
The following parameters need to check in Config tool.
ume.r3.connection.master.client -
ume.r3.connection.master.user -
ume.r3.connection.master.passwrd
ume.r3.connection.master.ashost
ume.r3.connection.master.sysnr
ume.datasource
Regards,
Ramana -
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 -
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 -
Com.sap.security.core.server.secstorefs.WrongKeyException
Hi,
we have done a system copy,while starting the java stack we are getting the below error.
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong..
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
... 15 more
Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.
at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
... 17 more
Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the decryption process.
at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
... 20 more
Caused by: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 30
at iaik.security.cipher.s.b(Unknown Source)
at iaik.security.cipher.w.a(Unknown Source)
at iaik.security.cipher.w.engineDoFinal(Unknown Source)
at javax.crypto.Cipher.doFinal(Unknown Source)
at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
... 21 more
#1.#000255334607000000000015000640DE00046E8629009A5B#1247422399420#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Loading: ConfigurationManager returned false! #
#1.#000255334607000000000017000640DE00046E8629009BC2#1247422399421#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Kernel not loaded. System halted.#
#1.#00025533460700000000001A000640DE00046E862908A703#1247422399948#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#######Thread[Thread-1,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]_2]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.cluster.impl6.JoinPortListener | toString: com.sap.engine.core.cluster.impl6.JoinPortListener@252e252e] with classloader [com.sap.engine.boot.CoreClassLoader@21d821d8]#
Regards,
SamHi,
Check with this note,
Note 791574 -
Also
Secure Storage for Application Specific Data
Applications or application components, deployed on the J2EE Engine, can save sensitive data
in encrypted form in a secure storage area in the J2EE Engineu2019s configuration database. The
data saved in this area is encrypted using a secret key that is created explicitly for the application
or service. The J2EE Engine uses the triple DES algorithm to perform the encryption.
You can use two approaches for storing and maintaining the encrypted data for the individual
applications or application components:
u2022 Centralized storage
With centralized storage, applications or application components use the Secure Storage
service on the J2EE Engine to encrypt and decrypt the data. This data is also stored in the
corresponding secure storage context on the J2EE Engine. You can control the
parameters of this secure storage area from the properties of the Configuration Manager.
For more information
u2022 Decentralized storage
With decentralized storage, the applications and application component maintain their own
storage area for the encrypted data. They only uses the Secure Storage service on the
J2EE Engine to retrieve the key, which is necessary to encrypt and decrypt the data.
Regards,
Ravi -
Where is com/sap/security/core/server/secstorefs/SecStoreFS?
Hi,
I am trying to create a Java client in NWDS that retrieves a DataSource object via JNDI from my XI 3.0 system.
I have added the jars I could think of (connector.jar, jta.jar, sapj2eeclient.jar, sapopensta.jar, etc.) to my build path.
When I attempt to retrieve the DataSource object via my Context I get the following exception:
java.lang.NoClassDefFoundError: com/sap/security/core/server/secstorefs/SecStoreFS
at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:798)
at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:113)
at com.sap.engine.services.dbpool.spi.DefaultConnectionManagerImpl.allocateConnection(DefaultConnectionManagerImpl.java:26)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
at com.hclaxon.xi.tools.CommsChannelConfigurator.createDBConnection(CommsChannelConfigurator.java:382)
at com.hclaxon.xi.tools.CommsChannelConfigurator.run(CommsChannelConfigurator.java:425)
at com.hclaxon.xi.tools.CommsChannelConfigurator.main(CommsChannelConfigurator.java:465)
Exception in thread "main"
Could someone please tell me which jar contains the class mentioned above?
thanks
BrianHi all,
Update to original question. I realised I was using a newer version of the openSQL api, so changed that.
Now I get a different execption:
java.lang.NoClassDefFoundError: com/sap/security/core/server/secstorefs/SecStoreFSException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructor0(Class.java:1930)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at com.sap.sql.connect.OpenSQLDataSource.newInstance(OpenSQLDataSource.java:148)
at com.sap.sql.connect.OpenSQLDataSource.newInstance(OpenSQLDataSource.java:133)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:102)
at com.sap.engine.services.dbpool.spi.DefaultConnectionManagerImpl.allocateConnection(DefaultConnectionManagerImpl.java:26)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
Can anyone tell me where this class is?
thanks
Brian -
Com/sap/security/core/server/secstorefs/SecStoreFS?
Hi,
I am trying to create a Java client in NWDS that retrieves a DataSource object via JNDI from my XI 3.0 system.
I have added the jars I could think of (connector.jar, jta.jar, sapj2eeclient.jar, sapopensta.jar, etc.) to my build path.
When I attempt to retrieve the DataSource object via my Context I get the following exception:
java.lang.NoClassDefFoundError: com/sap/security/core/server/secstorefs/SecStoreFS
at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:798)
at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:113)
at com.sap.engine.services.dbpool.spi.DefaultConnectionManagerImpl.allocateConnection(DefaultConnectionManagerImpl.java:26)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
at com.hclaxon.xi.tools.CommsChannelConfigurator.createDBConnection(CommsChannelConfigurator.java:382)
at com.hclaxon.xi.tools.CommsChannelConfigurator.run(CommsChannelConfigurator.java:425)
at com.hclaxon.xi.tools.CommsChannelConfigurator.main(CommsChannelConfigurator.java:465)
Exception in thread "main"
Could someone please tell me which jar contains the class mentioned above?
thanksHi,
Please try this, it may usefull for u.
tc_sec_secstorefs.jar in SDM\root\origin\sap.com\tc\sec\secstorefs\tc_sec_secstorefs.sda
Thanks & Regards,
Ravi. -
Start of UME Service Failed". Technical details: 'password' missing
Hi, I am facing a problem with UME Configuration of a Double Stack ABAP+Java Netweaver 7.01 System.
The Java Engine won't come up.
Though I have unlocked J2EE_ADMIN, J2EE_GUEST and SAPJSF in the ABAP User Management, after Restart of J2EE-Cluster the J2EE Engine doesnt't come up with the following Error (in std_server0.out):
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: 'password' missing 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:156) Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'password' missing 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.(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. Jun 16, 2010 8:07:30 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_59] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
When I try to reset the password of J2EE_ADMIN in the configtool the following message appears: "The value is different from previous!" Maybe this is 'cause I chose a password that I've used sometimes before, but when i enter something like '123456' or 'geheim' or something else the same message appears.
Please tell me how i can resolve the "The value is different from previous!"-Problem, because it's really critical by now. Thanks for your help.
regards,
CarstenHi Blanca,
First I have to thank you for your answer.
I followed the steps you provided:
the master client in the system is 100.
In client 100 the users SAPJSF, J2EE_ADMIN and J2EE_GUEST exist and are active.
I reset the password of SAPJSF on the ABAP side and after that in configtool i adjusted the values for
ume.r3.connection.master.client (100) and ume.r3.connection.master.user (SAPJSF).
But when it comes to save a new value for the *.master.passwd the same error appears.
"The value is different from previous!".
Any ideas?
thanks beforehand and regards
Carsten -
Java Server stopped -11113 - Start of UME service failed
Hi experts,
I've recently been deploying via JSPM the latest component versions for my recently upgraded netweaver system (7.0 EHP1 on Windows with MaxDB). Part way through I received errors and now the Java server is unable to start.
Below is some of the trace from "std_server0.out". I double checked the settings in the config tool and double checked the users in the ABAP system (SAPJSF and J2EE_GUEST), and everything seems to be fine, but I'm not an SAP J2EE expert so its very possible that I've overlooked something.
I've looked through the forums and for the most part people with this problem fixed it by unlocking SAPJSF, but I don't have that problem.
Any assistance is much appreciated. If more of this trace or data from another log file would help please let me know.
Cheers,
JB
70.190: [GC 70.190: [DefNew: 108794K->26118K(131328K), 0.1303850 secs] 108794K->26118K(1004800K), 0.1304744 secs]
Dec 10, 2009 7:40:56 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_65] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "CPIC-CALL: CMRCV on convId: 96069543
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /
parameter=conversation_ID / value=96069543 )
TIME Thu Dec 10 19:40:56 200
RELEASE 701
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 769
MODULE r3cpic.c
LINE 7341
COUNTER 5
". This message is critical if it appears during the startup of the AS Java.
Dec 10, 2009 7:40:56 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_65] 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: CPIC-CALL: CMRCV on convId: 96069543
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /
parameter=conversation_ID / value=96069543 )
TIME Thu Dec 10 19:40:56 200
RELEASE 701
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 769
MODULE r3cpic.c
LINE 7341
COUNTER 5
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:156)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: CPIC-CALL: CMRCV on convId: 96069543
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /
parameter=conversation_ID / value=96069543 )
TIME Thu Dec 10 19:40:56 200
RELEASE 701
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 769
MODULE r3cpic.c
LINE 7341
COUNTER 5
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: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 moreSomething that seemed odd in the error was: "200 RELEASE 701 COMPONENT CPIC (TCP/IP) with Unicode VERSION 3 RC 769 MODULE r3cpic.c LINE 7341 COUNTER 5"............So I updated the kernel and now everything works..
So for anyone with similar data in the trace updating kernel might be an option.
Cheers,
JB -
J2EE Engine cannot start after applying SP11 on WAS 6.40
Hi SAP
I am upgrading my WAS 6.40 SR1 java instance from SP9 to SP11. At the last stages of the installation the Java instance is stopped & started,at the step where Java instance is started, the 'server' process of the Java instance is not coming up properly. jcmon shows the dispatcher & SDM with status 'running' while server0 is with status 'stopped'.
Since I'm using ABAP as data source to the J2EE, appears to me that the problem is occuring due to password mismatch for user SAPJSF in R/3 client 168 & between user SAPJSF in J2EE though I'm not sure why the password might change in J2EE after applying SP11.
Please advice if my reasoning is correct, if no please advice how to solve this problem.
If yes pls advice how can I change the password for user SAPJSF in J2EE. FYI I already tried changing the password for user SAPJSF using the offline config tool, Under cluster-data-> Instance_ID87066 I select the
services com.sap.security.core.ume.service, then I select the ume.r3.connection.master.passwd, then the problem is inside the value option I'm not able to input the new password, neither I'm able to delete the old password, so the best thing I can do is Click on Set which opens a small window without any description with 2 options OK & Cancel, here I put the password same as R/3 password & save, after this I re-start the J2EE, but the same problem persists. Please advice on solving the problem.
Trace file std_server0.out shows that the foll error message......
Apr 28, 2005 8:09:47 PM com.sap.security.core.persistence
[SAPEngine_System_Thread[impl:5]_23] Fatal: User Management Engine
(com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect. Please re-enter". Connection data (obtained
from properties of UME service in section "ume.r3.connection.master.": "{
snc_qop=
client=168
abap_debug=
snc_myname=
gwserv=
snc_partnername=
ashost=CDBNTD03
group=
r3name=
snc_mode=0
gwhost=
sysnr=00
msserv=
poolmaxsize=10
snc_lib=
passwd=********
poolmaxwait=
trace=
receiverid_guest=master
mshost=
user=SAPJSF
lang=
receiverid=master
Apr 28, 2005 8:09:47 PM com.sap.security.core.persistence
[SAPEngine_System_Thread[impl:5]_23] Fatal: Initialization of UME persistence adapter "R3_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: Name or password is incorrect.
Please re-enter at com.sap.security.core.server.ume.service.UMEServiceFrame.start
(UMEServiceFrame.java:555)
at com.sap.engine.frame.ApplicationFrameAdaptor.start
(ApplicationFrameAdaptor.java:31)
at
com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:
201)
at com.sap.engine.core.service630.container.ServiceRunner.run
(ServiceRunner.java:142)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute
(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run
(SingleThread.java:145)
Caused by:
com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect. Please re-enter
at
com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3Persistenc
eBase.java:1707) at
com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init (R3PersistenceBase.java:1934)
std_server0.out (16%)
Thanks & Rgds,
AbhishekHi,
have a look here.
WebAS - invalid property value -
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 -
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. -
J2ee engine does not start - error 503
have a dual stack NetWeaver installation. I can start/connect to the ABAP stack fine, but I cannot connect to the Java stack.
When I do http://<machine name>:50000 or http://<machine name>:50000/irj/portal ... I get a "503 service unavailable. Application stopped" message.
searching through the j2ee logs did not reveal any problems (All j2ee services look like they are started successfully).Tiberiu,
Check ume service : com.sap.security.core.ume.service started or not?
I think it may be very slow and this may cause a lot of services to time out.
Changed settings in config tool:
1.instance_IDXXX -> server -> managers -> Service manager -> LoadTimeout from 5 to 15.
2.instance_IDXXX -> server -> managers -> ApplicationThreadManager there change InitialThreadCount, MinThreadCount and MaxThreadCount to 350.
3.Restart the server.
Regards,
Karthick Eswaran
*Do not forget to Reward points for helpful answers -
after PI-Upgrade to NW-PI-731-SP07, executing the PI-configuration wizard:
step 126 of 162
Assign SLD Data Supplier user to Group SAP_SLD_DATA_SUPPLIER (local SLD)
Error:
Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!
Execute Java Service
Library: sap.com/tc~lm~ctc~util~core_ear
Class: com.sap.ctc.util.core.services.UserFacade
Method: void com.sap.ctc.util.core.services.UserFacade.addUserToGroup(java.lang.String, java.lang.String)
Arguments (2)
userName : SLD_DS_EXE
groupName : SAP_SLD_DATA_SUPPLIER
InvokeService- Result: ERROR
Refresh Env. Messages: false
Duration: 1.936 sec
Library Info
Default Trace
Exception Class: com.sap.security.api.DuplicateKeyException
Exception Message: Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!
com.sap.security.api.DuplicateKeyException: Group found, but unique name "SAP_SLD_DATA_SUPPLIER" is not unique!
at com.sap.ctc.util.infra.rfc.BaseConfig.dispatchException(BaseConfig.java:230)
at com.sap.ctc.util.core.services.impl.ume.java.GroupJavaImpl.verify(GroupJavaImpl.java:121)
at com.sap.ctc.util.core.services.impl.ume.DualGroupImpl.verify(DualGroupImpl.java:118)
at com.sap.ctc.util.core.services.content.ume.UserService.addToGroup(UserService.java:725)
at com.sap.ctc.util.core.services.UserFacade.addUserToGroup(UserFacade.java:288)
what to do?
============
o.k.
https://service.sap.com/sap/support/notes/1016283
first run the UME consistency check => found some inconsistency => did repair UME
then run again UME consistency check => found no more inconsistency !!
the again - try to run the PI-Upgrade-Wizard => but again error on executing .....see this sap-notes:
http://service.sap.com/sap/support/notes/1617234
http://service.sap.com/sap/support/notes/1661135
http://service.sap.com/sap/support/notes/1678815
http://service.sap.com/sap/support/notes/1626747 -
Com.sap.isa.core.eai.BackendException: catalog.notFound
Hi,
I am getting this error in the defaultTrace.trc file when trying to log into the standard B2B shop:
005056A6001400150000000100000C740004A0D312DC8421#1302728322580#com.sap.isa.catalog.webcatalog.Web
CatInfo#sap.com/crm~b2b#com.sap.isa.catalog.webcatalog.WebCatInfo#Guest#0##n
/a##ce38233d661011e0c205000000867de2#SAPEngine_Application_Thread impl :3_27##0#0#Error##Plain###An
exception has occurred: BEM exception catalog.notFound(ERS300_001_001).
com.sap.isa.core.eai.BackendException: catalog.notFound(ERS300_001_001)
com.sap.isa.core.eai.BackendException: catalog.notFound(ERS300_001_001)
at com.sap.isa.catalog.webcatalog.WebCatInfo.init(WebCatInfo.java:395)
at com.sap.isa.businessobject.webcatalog.CatalogBusinessObjectManager.createCatalog(CatalogBusinessObjectManager.java:103)
I started getting this when we upgraded our sandbox ERP system to EHP4 and our ISA/E-commerce java apps to 7.0.
We also updated our ERP's OS to Windows Server 2008 R2 and SQL Server 2008R2.
The Java side is a Developer Workplace installed on Windows XP.
I have checked t-code WWM3 and ERS300_001_001 is there and there is data in it.
I checked SRMO and the indexes look fine as well as TREX. ( I have also deleted and recreated them)
All the connections seem good between ERP and TREX.
There are no short dumps or errors in ST22 or SM21.
ST11 doesn't have any error logs that I can see when I am trying to connect from B2B.
Any help would be greatly appreciated!
Thank you,
NeilThe issue was with the TREX configuration in Visual Administrator.
From Visual Administrator:
Server -> Services -> TREX Service
Then change nameserver.address to tcpip://<host>:<port>
Maybe you are looking for
-
My credit card was charged for two purchases in the amount of 14.95 each. I did not authorize these purchases. The purchase dates were 12/24 and 12/25.
-
Adding More Than 16 aUdio Tracks.
How do I add more than 16 Audio Tracks when my computer says there are no more audio tracks available?
-
[Solved] No screens configured error when i start X
hello all, im following the beginners guide for arch linux and installed it on a virtualbox vm and im trying to get X to work, and i added the lines to the /root/xorg.conf.new, and ran the X test, which worked. then i copied the .xinitrc file to my h
-
Mac storage is supposed to be 500gb but its only 399
can somone help me with this issue?(see the picture) Where did that 100gigs go?How do i get it back?
-
One stock code - different Sales codes (MATNR)
Hello! We are in the process industry wherein we stock in huge containers liquids which are sold in different sales codes (material numbers) according to different pack sizes. Process orders coming from SOs are used to make the goods ready into the M