- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- JAVA service ended with Error code -11113
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
JAVA service ended with Error code -11113
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 09-11-2009 7:28 AM
Hi everyone,
im using ECC 6 with AS ABAP , AS JAVA and SQL server 2005 Database installed in it.Now my ABAP service is running but JAVA server is down. J2EE Server is stopped with Exitcode -11113 in J2EE process table.But other two SDM and Dispatcher is working fine.
please help me to resolve this issue and make my JAVA service work
Thanks& regards,
Siva
- SAP Managed Tags:
- SAP NetWeaver Application Server
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello,
Can you paste the trace for std_server0.out since this would give the error in much more detail.
I can see only dev_disp and other logs.
The above mentioned std_server0.out log is very much important for analysing the error.
Regards,
Sangeetha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi sangeetha,
Herei is the log u asked me.
-
stdout/stderr redirect
-
node name : server0
pid : 3100
system name : SIL
system nr. : 00
started at : Wed Sep 16 13:21:33 2009
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 5736] 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 ... 2563 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 95 ms.
Loading: ThreadManager ... 126 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 506 ms.
Loading: LockingManager ... 127 ms.
Loading: ConfigurationManager ... 4067 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 190 ms.
Loading: ServiceManager ...
Loading services.:
Service memory started. (32 ms).
Service DQE started. (0 ms).
Service timeout started. (32 ms).
Service runtimeinfo started. (0 ms).
Service cross started. (3862 ms).
Service file started. (4463 ms).
Service trex.service started. (63 ms).
Service cafeuodi~mnuacc started. (0 ms).
Service p4 started. (6932 ms).
Service classpath_resolver started. (333 ms).
Service cafeucc~api started. (20271 ms).
Service userstore started. (16 ms).
Service jmx_notification started. (110 ms).
Service log_configurator started. (31649 ms).
Service naming started. (665 ms).
Service ts started. (64 ms).
Service locking started. (0 ms).
Service licensing started. (174 ms).
Service iiop started. (2643 ms).
Service failover started. (32 ms).
Service jmsconnector started. (174 ms).
Service http started. (570 ms).
Service appclient started. (32 ms).
Service javamail started. (2310 ms).
Service connector started. (206 ms).
Service webservices started. (1694 ms).
Service deploy started. (62839 ms).
Service configuration started. (79 ms).
Service MigrationService started. (32 ms).
Service bimmrdeployer started. (0 ms).
Service dbpool started. (3544 ms).
Service cafeugpmailcf started. (63 ms).
Sep 16, 2009 1:24:23 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_57] 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: "Password logon no longer possible - too many failed attempts". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=localhost
poolmaxwait=10000
}
".
Sep 16, 2009 1:24:23 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_57] 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: Password logon no longer possible - too many failed attempts
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
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: Password logon no longer possible - too many failed attempts
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.
Sep 16, 2009 1:24:23 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_57] 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 : 3100
system name : SIL
system nr. : 00
started at : Wed Sep 16 13:24:30 2009
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4896] 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 ... 3433 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 79 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 617 ms.
Loading: LockingManager ... 206 ms.
Loading: ConfigurationManager ... 2991 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 190 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service runtimeinfo started. (16 ms).
Service memory started. (16 ms).
Service timeout started. (47 ms).
Service cross started. (174 ms).
Service file started. (253 ms).
Service cafeuodi~mnuacc started. (0 ms).
Service trex.service started. (48 ms).
Service p4 started. (4225 ms).
Service classpath_resolver started. (174 ms).
Service cafeucc~api started. (8814 ms).
Service userstore started. (32 ms).
Service jmx_notification started. (64 ms).
Service log_configurator started. (18167 ms).
Service locking started. (48 ms).
Service naming started. (1503 ms).
Service ts started. (63 ms).
Service licensing started. (284 ms).
Service failover started. (15 ms).
Service javamail started. (1281 ms).
Service appclient started. (1045 ms).
Service iiop started. (3624 ms).
Service jmsconnector started. (143 ms).
Service http started. (522 ms).
Service connector started. (174 ms).
Service webservices started. (2722 ms).
Service deploy started. (58661 ms).
Service configuration started. (31 ms).
Service MigrationService started. (47 ms).
Service bimmrdeployer started. (95 ms).
Service dbpool started. (2911 ms).
Service cafeugpmailcf started. (47 ms).
Sep 16, 2009 1:26:15 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_88] 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: "Password logon no longer possible - too many failed attempts". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=localhost
poolmaxwait=10000
}
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
".
Sep 16, 2009 1:26:16 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_88] 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: Password logon no longer possible - too many failed attempts
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
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: Password logon no longer possible - too many failed attempts
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.
Sep 16, 2009 1:26:16 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_88] 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 : 3100
system name : SIL
system nr. : 00
started at : Wed Sep 16 13:26:19 2009
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4784] 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 ... 1171 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 95 ms.
Loading: ThreadManager ... 32 ms.
Loading: IpVerificationManager ... 15 ms.
Loading: ClassLoaderManager ... 32 ms.
Loading: ClusterManager ... 332 ms.
Loading: LockingManager ... 95 ms.
Loading: ConfigurationManager ... 2564 ms.
Loading: LicensingManager ... 32 ms.
Loading: CacheManager ... 174 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service memory started. (31 ms).
Service cafeuodi~mnuacc started. (0 ms).
Service cross started. (16 ms).
Service file started. (94 ms).
Service timeout started. (62 ms).
Service trex.service started. (47 ms).
Service runtimeinfo started. (16 ms).
Service cafeucc~api started. (267 ms).
Service p4 started. (456 ms).
Service classpath_resolver started. (47 ms).
Service userstore started. (31 ms).
Service jmx_notification started. (94 ms).
Service log_configurator started. (11820 ms).
Service locking started. (0 ms).
Service http started. (612 ms).
Service naming started. (863 ms).
Service ts started. (172 ms).
Service failover started. (141 ms).
Service appclient started. (141 ms).
Service licensing started. (47 ms).
Service jmsconnector started. (251 ms).
Service connector started. (346 ms).
Service iiop started. (361 ms).
Service javamail started. (1413 ms).
Service webservices started. (2339 ms).
Service deploy started. (50904 ms).
Service MigrationService started. (47 ms).
Service configuration started. (94 ms).
Service bimmrdeployer started. (16 ms).
Service dbpool started. (2731 ms).
Service cafeugpmailcf started. (47 ms).
Sep 16, 2009 1:27:37 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_61] 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: "Password logon no longer possible - too many failed attempts". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=localhost
poolmaxwait=10000
}
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
".
Sep 16, 2009 1:27:37 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_61] 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: Password logon no longer possible - too many failed attempts
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
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: Password logon no longer possible - too many failed attempts
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.
Sep 16, 2009 1:27:37 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_61] 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 : 3100
system name : SIL
system nr. : 00
started at : Wed Sep 16 13:27:40 2009
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 1592] 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 ... 643 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 63 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 251 ms.
Loading: LockingManager ... 95 ms.
Loading: ConfigurationManager ... 2527 ms.
Loading: LicensingManager ... 32 ms.
Loading: CacheManager ... 157 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service memory started. (32 ms).
Service timeout started. (15 ms).
Service runtimeinfo started. (16 ms).
Service cross started. (79 ms).
Service file started. (126 ms).
Service cafeuodi~mnuacc started. (0 ms).
Service trex.service started. (32 ms).
Service cafeucc~api started. (283 ms).
Service p4 started. (502 ms).
Service classpath_resolver started. (32 ms).
Service userstore started. (16 ms).
Service jmx_notification started. (267 ms).
Service log_configurator started. (11082 ms).
Service locking started. (0 ms).
Service naming started. (1020 ms).
Service http started. (910 ms).
Service jmsconnector started. (63 ms).
Service ts started. (235 ms).
Service failover started. (126 ms).
Service appclient started. (126 ms).
Service javamail started. (314 ms).
Service licensing started. (31 ms).
Service connector started. (299 ms).
Service iiop started. (502 ms).
Service webservices started. (565 ms).
Service deploy started. (50214 ms).
Service MigrationService started. (47 ms).
Service configuration started. (95 ms).
Service bimmrdeployer started. (31 ms).
Service dbpool started. (2684 ms).
Service cafeugpmailcf started. (63 ms).
Sep 16, 2009 1:28:54 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: "Password logon no longer possible - too many failed attempts". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
lang=EN
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=localhost
poolmaxwait=10000
}
".
Sep 16, 2009 1:28:54 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: Password logon no longer possible - too many failed attempts
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
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: Password logon no longer possible - too many failed attempts
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.
Sep 16, 2009 1:28:54 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.
Thanks &Regaards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
The Java-instance have problems with the connection to the ABAP-instance.
Please logon to the ABAP-instance in client 001 and unlock the user SAPJSF is locked in tcode SU01.
What is the reason for the user being locked?
Has the password been changed for this user?
In that case you have to change the password in the java-instance for that user also:
Use configtool to change parameter ume.r3.connection.master.passwd accordingly.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Siva,
This return code means that an essential service has failed to start. Check the related std_server.trc files to find more information regarding the faulty service and paste here the info if you need further help.
Regards,
Désiré
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
dev_disp: (this is in status YELLOW)
-
trc file: "dev_disp", trc level: 1, release: "700"
-
sysno 00
sid SIL
systemid 560 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 75
intno 20050900
make: multithreaded, Unicode, optimized
pid 212
Fri Sep 11 11:42:34 2009
kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)
length of sys_adm_ext is 572 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 212) [dpxxdisp.c 1237]
shared lib "dw_xml.dll" version 75 successfully loaded
shared lib "dw_xtc.dll" version 75 successfully loaded
shared lib "dw_stl.dll" version 75 successfully loaded
shared lib "dw_gui.dll" version 75 successfully loaded
shared lib "dw_mdm.dll" version 75 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Fri Sep 11 11:42:38 2009
WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0059.qqq.nxst) took 4 seconds
Fri Sep 11 11:42:43 2009
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5273]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >suranasvr1_SIL_00 <
DpShMCreate: sizeof(wp_adm) 18304 (1408)
DpShMCreate: sizeof(tm_adm) 3994272 (19872)
DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
DpShMCreate: sizeof(comm_adm) 528064 (1048)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1440)
DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 06E80040, size: 4653368)
DpShMCreate: allocated sys_adm at 06E80040
DpShMCreate: allocated wp_adm at 06E81E40
DpShMCreate: allocated tm_adm_list at 06E865C0
DpShMCreate: allocated tm_adm at 06E865F0
DpShMCreate: allocated wp_ca_adm at 07255890
DpShMCreate: allocated appc_ca_adm at 0725B650
DpShMCreate: allocated comm_adm at 0725D590
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 072DE450
DpShMCreate: allocated gw_adm at 072DE490
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 072DE4C0
DpShMCreate: allocated wall_adm at 072DE4C8
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
Fri Sep 11 11:42:44 2009
J2EE server info
start = TRUE
state = STARTED
pid = 2060
argv[0] = D:\usr\sap\SIL\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\SIL\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1857
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=SIL
argv[7] = -DSAPMYNAME=suranasvr1_SIL_00
argv[8] = -DSAPPROFILE=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
Fri Sep 11 11:42:45 2009
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1623]
Fri Sep 11 11:42:46 2009
***LOG Q0K=> DpMsAttach, mscon ( suranasvr1) [dpxxdisp.c 11586]
DpStartStopMsg: send start message (myname is >suranasvr1_SIL_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Fri Sep 11 11:42:47 2009
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 75
Release check o.K.
Fri Sep 11 11:43:32 2009
MBUF state ACTIVE
Fri Sep 11 11:43:33 2009
DpModState: change server state from STARTING to ACTIVE
Fri Sep 11 11:45:36 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1512
(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1859) [nixxi.cpp 4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2060)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Fri Sep 11 11:45:46 2009
J2EE server info
start = TRUE
state = STARTED
pid = 3732
argv[0] = D:\usr\sap\SIL\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\SIL\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1965
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=SIL
argv[7] = -DSAPMYNAME=suranasvr1_SIL_00
argv[8] = -DSAPPROFILE=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Fri Sep 11 11:47:05 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1464
(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1967) [nixxi.cpp 4235]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3732)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Fri Sep 11 11:47:06 2009
J2EE server info
start = TRUE
state = STARTED
pid = 2604
argv[0] = D:\usr\sap\SIL\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\SIL\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=1997
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=SIL
argv[7] = -DSAPMYNAME=suranasvr1_SIL_00
argv[8] = -DSAPPROFILE=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
expecting your valuable resonse
thanks & regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
please paste the error log dev_dispatcher, dev_server0, jvm_* and other related logs.
This can help up find solution. Did u applied note 723909?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Error and its following log has been paster here
dev_server0 )this is in status Grey)
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
**********************************************************************
[Thr 1044] JLaunchCloseProgram: good bye (exitcode = -11113)
-
trc file: "D:\usr\sap\SIL\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
-
node name : ID9967450
pid : 6140
system name : SIL
system nr. : 00
started at : Fri Sep 11 11:51:17 2009
arguments :
arg[00] : D:\usr\sap\SIL\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
arg[02] : -DSAPINFO=SIL_00_server
arg[03] : pf=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1999
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=SIL
arg[08] : -DSAPMYNAME=suranasvr1_SIL_00
arg[09] : -DSAPPROFILE=D:\usr\sap\SIL\SYS\profile\SIL_DVEBMGS00_suranasvr1
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 2972] Fri Sep 11 11:51:17 2009
[Thr 2972] *** WARNING => INFO: Unknown property [instance.box.number=SILDVEBMGS00suranasvr1] [jstartxx.c 841]
[Thr 2972] *** WARNING => INFO: Unknown property [instance.en.host=suranasvr1] [jstartxx.c 841]
[Thr 2972] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 2972] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : suranasvr1
-> ms port : 3901
-> OS libs : D:\usr\sap\SIL\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host : suranasvr1
-> ms port : 3901
-> os libs : D:\usr\sap\SIL\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9967400 : D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9967450 : D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************
**********************************************************************
Worker nodes
-> [00] ID9967400 : D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID9967450 : D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************
[Thr 2972] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 2972] JLaunchRequestQueueInit: create pipe listener thread
[Thr 3720] JLaunchRequestFunc: Thread 3720 started as listener thread for np messages.
[Thr 3444] WaitSyncSemThread: Thread 3444 started as semaphore monitor thread.
[Thr 2972] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 2972] CPIC (version=700.2005.12.02)
[Thr 2972] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 2972] Fri Sep 11 11:51:18 2009
[Thr 2972] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SIL\DVEBMGS00\exe\jvmx.jar
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
where exactly i could find these files
i have some files available in D:\usr\sap\SIL\DVEBMGS00\work
jvm_bootstrap.o00,
jvm_bootstrap.o01,
jvm_bootstrap.out,
jvm_bootstrap_ID9967400.o00,
jvm_bootstrap_ID9967400.o01,
jvm_bootstrap_ID9967400.out,
jvm_bootstrap_ID9967450.o00,
jvm_bootstrap_ID9967450.o01
jvm_bootstrap_ID9967450.out
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
jvm_bootstrap_ID9967400.o00
-
Bootstrap MODE:
<SINGLE INSTANCE>
determined by parameter [ID009967400].
-
Missing RunningMode property - runningin NORMAL mode.
+--
[ DB info ]--
| Cluster ID in DB : ID9967400
| Type : dispatcher
| Installation Local Home : .\dispatcher
| OS : ntintel
| Unicode support : nuc
| Bit-length : 32
| Binaries Synch Status : 2
| Database bin version : 290
| Local bin version : 290
+----
Synchronizing configuration...
No local properties available for [ConnectionsManipulator].
No local properties available for [LicensingManager].
No local properties available for [ClassLoaderManager].
No local properties available for [PoolManager].
No local properties available for [LogManager].
No local properties available for [CacheManager].
No local properties available for [IpVerificationManager].
No local properties available for [kernel_shell_commands].
No local properties available for [PortsManager].
No local properties available for [LockingManager].
No local properties available for [ThreadManager].
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\cfg\kernel\log-configuration.xml].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\cfg\kernel\enqt.pf].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\cfg\kernel\kernel.properties].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\cfg\kernel\hosts.txt].
...Synched ok!
Ok! (219 ms)
Synchronizing binaries...
Ok! synched: 0 file(s); deleted: 0 file(s) (0 ms)
Synchronizing additional files...
Synchronizing file [.\dispatcher\version.txt].
...Synched ok!
Synchronizing file [.\dispatcher\.hotspot_compiler].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\java.policy].
...Synched ok!
Ok! (15 ms)
Synchronizing DTD files...
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\dtd\library.provider.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\dtd\service.provider.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\dtd\interface.provider.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\dtd\monitor-configuration.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\dispatcher\dtd\log-configuration.dtd].
...Synched ok!
Ok! (47 ms)
Done!
Synch time: 2515 ms
-
jvm_bootstrap_ID9967450.o00
-
Bootstrap MODE:
<SINGLE INSTANCE>
determined by parameter [ID009967450].
-
Missing RunningMode property - runningin NORMAL mode.
+--
[ DB info ]--
| Cluster ID in DB : ID9967450
| Type : server
| Installation Local Home : .\server0
| OS : ntintel
| Unicode support : nuc
| Bit-length : 32
| Binaries Synch Status : 2
| Database bin version : 290
| Local bin version : 290
+----
Synchronizing configuration...
No local properties available for [ApplicationThreadManager].
No local properties available for [LicensingManager].
No local properties available for [ClassLoaderManager].
No local properties available for [PoolManager].
No local properties available for [LogManager].
No local properties available for [CacheManager].
No local properties available for [IpVerificationManager].
No local properties available for [kernel_shell_commands].
No local properties available for [ThreadManager].
No local properties available for [LockingManager].
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\cfg\kernel\log-configuration.xml].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\cfg\kernel\enqt.pf].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\cfg\kernel\kernel.properties].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\cfg\kernel\hosts.txt].
...Synched ok!
Ok! (250 ms)
Synchronizing binaries...
Ok! synched: 0 file(s); deleted: 0 file(s) (0 ms)
Synchronizing additional files...
Synchronizing file [.\server0\version.txt].
...Synched ok!
Synchronizing file [.\server0\.hotspot_compiler].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\META-INF\mailcap].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\META-INF\javamail.default.providers].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\remote.policy].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\java.policy].
...Synched ok!
Ok! (94 ms)
Synchronizing DTD files...
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\library.provider.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\interface.provider.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\jms-destinations.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\jms-factories.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\data-source-aliases.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\appclient-j2ee-engine.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\data-sources.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\log-configuration.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\connector-j2ee-engine.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\persistent.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\web-j2ee-engine.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\service.provider.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\ejb-j2ee-engine.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\monitor-configuration.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\application-j2ee-engine.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\application-client-additional.dtd].
...Synched ok!
Synchronizing file [D:\usr\sap\SIL\DVEBMGS00\j2ee\cluster\server0\dtd\db-init.dtd].
...Synched ok!
Ok! (140 ms)
Done!
Synch time: 2781 ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
jvm_bootstrap.o00
-
Bootstrap MODE:
<INSTANCE GLOBALS>
determined by parameter [ID0099674].
-
Missing RunningMode property - runningin NORMAL mode.
Instance [ID99674] will run in [NORMAL] mode, performing action [NONE]
Discovered property [instance.en.port] with value [3201] !
Discovered property [instance.en.host] with value [suranasvr1] !
Synchronizing file [.\.hotspot_compiler].
...Synched ok!
Synchronizing file [..\..\SDM\program\.hotspot_compiler].
...Synched ok!
Synch time: 2406 ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- CAP odata-v2-adapter: batch request is not supported? in Technology Q&A
- Consuming on-Premise Service in CAP Project in Technology Q&A
- using Already availble XSUAA service to another application giving service broker failed error in Technology Q&A
- Sorting not working on object Page Item table SAP CAP BTP Fiori elements in Technology Q&A
- Support for API Business Hub Enterprise in Actions Project in Technology Blogs by SAP
| User | Count |
|---|---|
| 85 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.