- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Connection to SAP gateway failed
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Connection to SAP gateway failed
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 09-11-2006 6:41 AM
Hello All,
I hv created connected Portal System with R/3 test system and for that i hv defined the necessary parametrs in UM Configuration and created system object for test system in Portal.Till now everything was working fine,tday suddenly an issue occured saying:
<b>----
stdout/stderr redirect
-
node name : server0
pid : 1916
system name : EPD
system nr. : 00
started at : Mon Sep 11 09:37:06 2006
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 iaik/security/md/SHA a
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
SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...
Loading: LogManager ... 2094 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 656 ms.
Loading: ThreadManager ... 344 ms.
Loading: IpVerificationManager ... 47 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 1625 ms.
Loading: LockingManager ... 1203 ms.
Loading: ConfigurationManager ... 5547 ms.
Loading: LicensingManager ... 219 ms.
Loading: ServiceManager ...
Loading services.:
Service memory started. (47 ms).
Service runtimeinfo started. (16 ms).
Service timeout started. (31 ms).
Service cross started. (2672 ms).
Service file started. (1531 ms).
Service jmx_notification started. (31 ms).
Service trex.service started. (422 ms).
Service p4 started. (860 ms).
Service classpath_resolver started. (438 ms).
0.000: [GC 0.000: [ParNew: 87040K->7305K(130560K), 0.1020948 secs] 87040K->7305K(1005056K), 0.1021817 secs]
Service tcsecwssec~service started. (1765 ms).
Service userstore started. (16 ms).
Service tcsecvsi~service started. (188 ms).
Service deploy started. (7109 ms).
Service apptracing started. (219 ms).
Service log_configurator started. (18875 ms).
Service http started. (562 ms).
Service naming started. (594 ms).
Service ts started. (78 ms).
Service locking started. (0 ms).
Service appclient started. (47 ms).
Service licensing started. (32 ms).
Service jmsconnector started. (63 ms).
Service failover started. (16 ms).
Service javamail started. (359 ms).
Service connector started. (282 ms).
Service webservices started. (1860 ms).
Service configuration started. (63 ms).
Service dbpool started. (5781 ms).
16.695: [GC 16.695: [ParNew: 94344K->10519K(130560K), 0.1102524 secs] 94344K->10519K(1005056K), 0.1103400 secs]
Sep 11, 2006 9:38:37 AM ...asource.imp.R3Persistence.doInitRfc() [SAPEngine_System_Thread[impl:5]_30] 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: "Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:38:37 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
jco.client.lang=EN
jco.client.user=portaltest
jco.client.mshost=r3dev
jco.client.snc_myname=
jco.client.receiverid_guest=master
jco.client.group=SPACE
jco.client.snc_lib=
jco.client.sysnr=05
jco.client.client=090
jco.client.poolmaxsize=10
jco.client.trace=
jco.client.abap_debug=
jco.client.gwserv=sapgw05
jco.client.poolmaxwait=
jco.client.ashost=10.10.100.186
jco.client.snc_mode=
jco.client.r3name=T11
jco.client.snc_qop=
jco.client.gwhost=r3dev
jco.client.msserv=
jco.client.receiverid=master
jco.client.passwd=********
jco.client.snc_partnername=
}
".
Sep 11, 2006 9:38:37 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_30] 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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:38:37 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:38:37 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
com.sap.engine.frame.ServiceException: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:38:37 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:38:37 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 11, 2006 9:38:37 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_30] 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 : 1916
system name : EPD
system nr. : 00
started at : Mon Sep 11 09:38:41 2006
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 iaik/security/md/SHA a
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
SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...
Loading: LogManager ... 906 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 984 ms.
Loading: ThreadManager ... 47 ms.
Loading: IpVerificationManager ... 31 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 453 ms.
Loading: LockingManager ... 125 ms.
Loading: ConfigurationManager ... 2922 ms.
Loading: LicensingManager ... 62 ms.
Loading: ServiceManager ...
Loading services.:
Service cross started. (187 ms).
Service file started. (172 ms).
Service memory started. (218 ms).
Service trex.service started. (281 ms).
Service jmx_notification started. (266 ms).
Service runtimeinfo started. (16 ms).
Service timeout started. (31 ms).
Service userstore started. (16 ms).
Service tcsecvsi~service started. (860 ms).
Service tcsecwssec~service started. (812 ms).
Service p4 started. (688 ms).
Service classpath_resolver started. (32 ms).
0.000: [GC 0.000: [ParNew: 87039K->7244K(130560K), 0.1068666 secs] 87039K->7244K(1005056K), 0.1069803 secs]
Service deploy started. (4438 ms).
Service apptracing started. (625 ms).
Service log_configurator started. (10125 ms).
Service locking started. (0 ms).
Service naming started. (656 ms).
Service failover started. (93 ms).
Service appclient started. (188 ms).
Service ts started. (187 ms).
Service jmsconnector started. (578 ms).
Service licensing started. (78 ms).
Service javamail started. (766 ms).
Service connector started. (766 ms).
Service configuration started. (203 ms).
Service webservices started. (1437 ms).
Service http started. (2765 ms).
Service dbpool started. (7000 ms).
16.634: [GC 16.634: [ParNew: 94284K->10896K(130560K), 0.1195574 secs] 94284K->10896K(1005056K), 0.1196569 secs]
Sep 11, 2006 9:39:38 AM ...asource.imp.R3Persistence.doInitRfc() [SAPEngine_System_Thread[impl:5]_27] 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: "Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:39:38 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
jco.client.lang=EN
jco.client.user=portaltest
jco.client.mshost=r3dev
jco.client.snc_myname=
jco.client.receiverid_guest=master
jco.client.group=SPACE
jco.client.snc_lib=
jco.client.sysnr=05
jco.client.client=090
jco.client.poolmaxsize=10
jco.client.trace=
jco.client.abap_debug=
jco.client.gwserv=sapgw05
jco.client.poolmaxwait=
jco.client.ashost=10.10.100.186
jco.client.snc_mode=
jco.client.r3name=T11
jco.client.snc_qop=
jco.client.gwhost=r3dev
jco.client.msserv=
jco.client.receiverid=master
jco.client.passwd=********
jco.client.snc_partnername=
}
".
Sep 11, 2006 9:39:38 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_27] 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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:39:38 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:39:38 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
com.sap.engine.frame.ServiceException: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:39:38 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:39:38 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 11, 2006 9:39:38 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_27] 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 : 1916
system name : EPD
system nr. : 00
started at : Mon Sep 11 09:39:42 2006
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 iaik/security/md/SHA a
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
SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...
Loading: LogManager ... 1063 ms.
Loading: PoolManager ... 15 ms.
Loading: ApplicationThreadManager ... 1516 ms.
Loading: ThreadManager ... 312 ms.
Loading: IpVerificationManager ... 79 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 453 ms.
Loading: LockingManager ... 187 ms.
Loading: ConfigurationManager ... 3797 ms.
Loading: LicensingManager ... 47 ms.
Loading: ServiceManager ...
Loading services.:
Service memory started. (234 ms).
Service cross started. (219 ms).
Service file started. (265 ms).
Service runtimeinfo started. (47 ms).
Service jmx_notification started. (234 ms).
Service userstore started. (0 ms).
Service trex.service started. (828 ms).
Service timeout started. (719 ms).
Service tcsecvsi~service started. (844 ms).
Service tcsecwssec~service started. (985 ms).
Service p4 started. (907 ms).
Service classpath_resolver started. (16 ms).
0.000: [GC 0.000: [ParNew: 87039K->7252K(130560K), 0.1056036 secs] 87039K->7252K(1005056K), 0.1056966 secs]
Service deploy started. (4579 ms).
Service apptracing started. (157 ms).
Service log_configurator started. (10703 ms).
Service locking started. (31 ms).
Service http started. (375 ms).
Service naming started. (485 ms).
Service failover started. (78 ms).
Service jmsconnector started. (422 ms).
Service appclient started. (422 ms).
Service ts started. (407 ms).
Service connector started. (391 ms).
Service licensing started. (94 ms).
Service javamail started. (578 ms).
Service configuration started. (47 ms).
Service webservices started. (1031 ms).
Service dbpool started. (6265 ms).
15.524: [GC 15.524: [ParNew: 94292K->10861K(130560K), 0.1096814 secs] 94292K->10861K(1005056K), 0.1097663 secs]
Sep 11, 2006 9:40:40 AM ...asource.imp.R3Persistence.doInitRfc() [SAPEngine_System_Thread[impl:5]_26] 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: "Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:40:40 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
jco.client.lang=EN
jco.client.user=portaltest
jco.client.mshost=r3dev
jco.client.snc_myname=
jco.client.receiverid_guest=master
jco.client.group=SPACE
jco.client.snc_lib=
jco.client.sysnr=05
jco.client.client=090
jco.client.poolmaxsize=10
jco.client.trace=
jco.client.abap_debug=
jco.client.gwserv=sapgw05
jco.client.poolmaxwait=
jco.client.ashost=10.10.100.186
jco.client.snc_mode=
jco.client.r3name=T11
jco.client.snc_qop=
jco.client.gwhost=r3dev
jco.client.msserv=
jco.client.receiverid=master
jco.client.passwd=********
jco.client.snc_partnername=
}
".
Sep 11, 2006 9:40:40 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_26] 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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:40:40 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:40:40 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
com.sap.engine.frame.ServiceException: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:40:40 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:40:40 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 11, 2006 9:40:40 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_26] 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 : 1916
system name : EPD
system nr. : 00
started at : Mon Sep 11 09:40:42 2006
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 iaik/security/md/SHA a
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
SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...
Loading: LogManager ... 1125 ms.
Loading: PoolManager ... 15 ms.
Loading: ApplicationThreadManager ... 1047 ms.
Loading: ThreadManager ... 47 ms.
Loading: IpVerificationManager ... 31 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 516 ms.
Loading: LockingManager ... 141 ms.
Loading: ConfigurationManager ... 3687 ms.
Loading: LicensingManager ... 63 ms.
Loading: ServiceManager ...
Loading services.:
Service cross started. (156 ms).
Service file started. (204 ms).
Service memory started. (219 ms).
Service jmx_notification started. (203 ms).
Service trex.service started. (390 ms).
Service runtimeinfo started. (15 ms).
Service p4 started. (297 ms).
Service classpath_resolver started. (79 ms).
Service userstore started. (16 ms).
Service tcsecvsi~service started. (1297 ms).
Service timeout started. (1109 ms).
Service tcsecwssec~service started. (1875 ms).
0.000: [GC 0.000: [ParNew: 87039K->7282K(130560K), 0.1036058 secs] 87039K->7282K(1005056K), 0.1036990 secs]
Service deploy started. (5718 ms).
Service apptracing started. (641 ms).
Service log_configurator started. (11500 ms).
Service locking started. (16 ms).
Service http started. (422 ms).
Service naming started. (610 ms).
Service failover started. (78 ms).
Service appclient started. (188 ms).
Service jmsconnector started. (218 ms).
Service ts started. (360 ms).
Service licensing started. (47 ms).
Service connector started. (453 ms).
Service configuration started. (47 ms).
Service javamail started. (625 ms).
Service webservices started. (1016 ms).
Service dbpool started. (6750 ms).
15.562: [GC 15.562: [ParNew: 94315K->10780K(130560K), 0.1101587 secs] 94315K->10780K(1005056K), 0.1102443 secs]
Sep 11, 2006 9:41:42 AM ...asource.imp.R3Persistence.doInitRfc() [SAPEngine_System_Thread[impl:5]_20] 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: "Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:41:42 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
jco.client.lang=EN
jco.client.user=portaltest
jco.client.mshost=r3dev
jco.client.snc_myname=
jco.client.receiverid_guest=master
jco.client.group=SPACE
jco.client.snc_lib=
jco.client.sysnr=05
jco.client.client=090
jco.client.poolmaxsize=10
jco.client.trace=
jco.client.abap_debug=
jco.client.gwserv=sapgw05
jco.client.poolmaxwait=
jco.client.ashost=10.10.100.186
jco.client.snc_mode=
jco.client.r3name=T11
jco.client.snc_qop=
jco.client.gwhost=r3dev
jco.client.msserv=
jco.client.receiverid=master
jco.client.passwd=********
jco.client.snc_partnername=
}
".
Sep 11, 2006 9:41:42 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_20] 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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:41:42 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:41:42 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
com.sap.engine.frame.ServiceException: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:41:42 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)
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: Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=r3dev GROUP=SPACE R3NAME=T11 MSSERV=sapmsT11 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 192.168.100.186, service 3305)
TIME Mon Sep 11 09:41:42 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8588
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:2099)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:2315)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 11, 2006 9:41:42 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_20] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.</b>
Although i hv checked all the parametrs in Backend,they r same and working fine but iam still facing this issue?can someone plz help me out where shld i look for inorder to find out the faulty parameter and how to resolve this issue? My Email Id is reachme.saumya@gmail.com .
I need a solution to this on urgent basis,Kindly revert at earliest.
regards,
Saumya
- SAP Managed Tags:
- PORTAL Administration and Development
Accepted Solutions (0)
Answers (1)
Answers (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello!
Was this issue resolved?
We have the same problem.
Please tell me.
Masahide Yano
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
- SAC BW live connection: Error Illegal State: data area already existing in Technology Q&A
- What are steps and prerequisite to create a content repository using CMIS as a content server in Technology Q&A
- Unable to log in to SAP BusinessObjects CMC in Technology Blogs by Members
- Connection restrictions and their relation to user groups in SAP HANA Cloud, SAP HANA Database in Technology Blogs by SAP
- Retrieve metadata failed because the OData server returned HTTP code, 401 in Technology Q&A
| User | Count |
|---|---|
| 90 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.