- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- SAPJSF being locked consistently
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
SAPJSF being locked consistently
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-02-2008 3:42 PM
Hi all,
I have installed a XI server on SR2...
I had a problem in which the DDIC and SAP* users id were not reseted ... it didnt ask for new passwords
I know i can solve this problem by either using the master password oe deleting the SAP* user from the table and reseting it to a new pass.
My problem rather is with the SAPJSF user which is constantly getting locked...
evry time i stop and start the server...
please let me knw wht could the problem be...
The logs of server 0 says the following
#1.5#00137272678800630000041500001100000442BE78EAAF5A#1199285746675#com.sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()#J2EE_GUEST#0####72e5a590b92a11dc8f59001372726788#Thread[Thread-59,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Java###Exception in method: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
[EXCEPTION]
#1#com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory. at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261) at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624) at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271) at javax.naming.InitialContext.lookup(InitialContext.java:347) at javax.naming.InitialContext.lookup(InitialContext.java:347) at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1238) at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1182) at java.lang.Thread.run(Thread.java:534) # It was the above logg before the server being restarted and after restating it says the following #1.5#00137272678800690000003500001100000442BE9926A665#1199286287496#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase#sap.com/com.sap.aii.af.app#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.searchPrincipalDatabags()#J2EE_GUEST#0####0e5fb420b94411dcbd03001372726788#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector. Message: .##An exception was thrown in the UME/ABAP user management connector. Message: . [EXCEPTION] #2#Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=localhost SYSNR=01 GWHOST=localhost GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '127.0.0.1:sapgw01' not reached TIME Wed Jan 02 20:34:47 2008 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2770 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1 #com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=localhost SYSNR=01 GWHOST=localhost GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '127.0.0.1:sapgw01' not reached TIME Wed Jan 02 20:34:47 2008 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2770 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178) at com.sap.security.core.persistence.datasource.imp.R3Persistence.searchPrincipalDatabags(R3Persistence.java:1405) at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.searchPrincipalDatabagsInternal(PrincipalDatabagFactoryInstance.java:4424) at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.searchPrincipalDatabags(PrincipalDatabagFactoryInstance.java:3936) at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:360) at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56) at com.sap.security.core.imp.UserAccountFactory.getReadonlyUserAccountByLogonId(UserAccountFactory.java:672) at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1248) at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1285) at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1300) at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:59) at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98) at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395) at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327) at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258) at com.sap.aii.utilxi.rtcheck.mx.PrivilegedDeregistration.run(PrivilegedDeregistration.java:79) at java.security.AccessController.doPrivileged(Native Method) at com.sap.aii.utilxi.rtcheck.mx.PrivilegedDeregistration.execute(PrivilegedDeregistration.java:57) at com.sap.aii.utilxi.rtcheck.mx.SapAgentImpl.unregisterMBean(SapAgentImpl.java:229) at com.sap.aii.utilxi.rtcheck.mx.BaseAgent.unregisterMBean(BaseAgent.java:99) at com.sap.aii.utilxi.rtcheck.mx.XIJ2EEComponentBuilder.unregister(XIJ2EEComponentBuilder.java:55) at com.sap.aii.utilxi.rtcheck.mx.XIJ2EEComponentDirector.unregister(XIJ2EEComponentDirector.java:115) at com.sap.aii.af.servlet.AdapterFrameworkServlet.unregisterAdapterEngineCCMSProvider(AdapterFrameworkServlet.java:155) at com.sap.aii.af.servlet.AdapterFrameworkServlet.destroy(AdapterFrameworkServlet.java:104) at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722) at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) -
caused by -
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=localhost SYSNR=01 GWHOST=localhost GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '127.0.0.1:sapgw01' not reached TIME Wed Jan 02 20:34:47 2008 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2770 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1 at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:989) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3193) at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5314) at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6065) at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6015) at com.sap.mw.jco.JCO.getClient(JCO.java:8663) at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.fetchClient(R3JCo640Proxy.java:441) at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.execute(R3JCo640Proxy.java:367) at com.sap.security.core.persistence.datasource.imp.R3Persistence.doBapiUserExistenceCheck(R3Persistence.java:7305) at com.sap.security.core.persistence.datasource.imp.R3Persistence.getExistenceCheckResult(R3Persistence.java:2753) at com.sap.security.core.persistence.datasource.imp.R3Persistence.searchPrincipalDatabags(R3Persistence.java:1227) at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.searchPrincipalDatabagsInternal(PrincipalDatabagFactoryInstance.java:4424) at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.searchPrincipalDatabags(PrincipalDatabagFactoryInstance.java:3936) at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:360) at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56) at com.sap.security.core.imp.UserAccountFactory.getReadonlyUserAccountByLogonId(UserAccountFactory.java:672) at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1248) at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1285) at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1300) at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:59) at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98) at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395) at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327) at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258) at com.sap.aii.utilxi.rtcheck.mx.PrivilegedDeregistration.run(PrivilegedDeregistration.java:79) at java.security.AccessController.doPrivileged(Native Method) at com.sap.aii.utilxi.rtcheck.mx.PrivilegedDeregistration.execute(PrivilegedDeregistration.java:57) at com.sap.aii.utilxi.rtcheck.mx.SapAgentImpl.unregisterMBean(SapAgentImpl.java:229) at com.sap.aii.utilxi.rtcheck.mx.BaseAgent.unregisterMBean(BaseAgent.java:99) at com.sap.aii.utilxi.rtcheck.mx.XIJ2EEComponentBuilder.unregister(XIJ2EEComponentBuilder.java:55) at com.sap.aii.utilxi.rtcheck.mx.XIJ2EEComponentDirector.unregister(XIJ2EEComponentDirector.java:115) at com.sap.aii.af.servlet.AdapterFrameworkServlet.unregisterAdapterEngineCCMSProvider(AdapterFrameworkServlet.java:155) at com.sap.aii.af.servlet.AdapterFrameworkServlet.destroy(AdapterFrameworkServlet.java:104) at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722) at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) # #1.5#001372726788001E00000012000016DC000442BEAA9C1477#1199286580414#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_77##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.# #1.5#00137272678800210000000200000F80000442BEAC60D22B#1199286610086#com.sap.security.core.persistence##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_99##0#0#Fatal#1#/System/Security/Usermanagement#Java#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: "". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "".##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: "". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "".#2#Password logon no longer possible - too many failed attempts#{
passwd=********
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=localhost
poolmaxwait=10000
}
#
#1.5#00137272678800210000000400000F80000442BEAC60DE29#1199286610086#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase##com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init()#######SAPEngine_System_Thread[impl:5]_99##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector. Message: .##An exception was thrown in the UME/ABAP user management connector. Message: .
[EXCEPTION]
#2#Password logon no longer possible - too many failed attempts#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)
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.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts
at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.getAttributes(R3JCo640Proxy.java:408)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.doInitRfc(R3PersistenceBase.java:689)
at com.sap.security.core.persistence.datasource.imp.R3Persistence.localInitialization(R3Persistence.java:276)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:424)
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)
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)
This is what the last lines suggest
#
#1.5#00137272678800210000001200000F80000442BEAC60FC7D#1199286610086#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_99##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
I have not put in the whole log bt selleted only the few logs which has caused an error.
My server0 is down saying tht it had to exit suddenly ......with exit code-11113
The following is the developer trace of server0
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [server0]
**********************************************************************
[Thr 1928] Wed Jan 02 20:39:44 2008
[Thr 1928] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1928] Wed Jan 02 20:39:45 2008
[Thr 1928] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1928] JLaunchISetClusterId: set cluster id 14573850
[Thr 1928] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1928] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5164] Wed Jan 02 20:40:09 2008
[Thr 5164] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 5164] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 3096] Wed Jan 02 20:40:10 2008
[Thr 3096] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 3096] **********************************************************************
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 3096] JLaunchCloseProgram: good bye (exitcode = -11113)
Rgds
Aditya
- SAP Managed Tags:
- SAP Process Integration
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Aditya,
please check for consistent passwords of SAPJSF user on ABAP and J2EE Engine side.
Check with Configtool > Global Server Configuration > services >
com.sap.security.core.ume.service > ume.r3.connection.master.passwd.
This should be the only place where the SAPJSF password is kept on J2EE Engine side.
An ABAP side the SAPJSF User should be created as System or Communication User,
so that no password change is requested during logon.
Hope this helps,
Silvia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Answers (1)
Answers (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Any one can put light on this matter
Rgds
aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- More than 2250 data products ready to pimp your analytics in Technology Blogs by SAP
- Planning Sequence with Packaging failing in process chain in Technology Q&A
- SAPJSF user gets frequently locked in Technology Blogs by Members
- Do you know the Deadlock Monitor? in Technology Blogs by SAP
- SAP Identity Management Customer Connection 2021: Interim Report! in Technology Blogs by SAP
| User | Count |
|---|---|
| 85 | |
| 10 | |
| 10 | |
| 9 | |
| 6 | |
| 6 | |
| 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.