on 04-29-2009 8:13 PM
Hello all,
An attempt was made to start an ECC 6.0 box (with J2EE and ABAP stacks). The ABAP portion starts fine (as one can log into it) but the J2EE portion has failed. Below are files that were gathered. It looks like it is due to a UME error.
TIA
jcmon pf=/usr/sap/KDE/SYS/profile/KDE_DVEBMGS30_nala
Idx | Name | PID | State | Error | Restart |
--- | |||||
0 | dispatcher | 5594 | Running | 0 | yes |
1 | server0 | 0 | Stopped | 4 | no |
2 | SDM | 5596 | Running | 0 | yes |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
from file: /usr/sap/KDX/DVEBMGS30/work/dev_server0
**********************************************************************
[Thr 1105529168] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [server0]
**********************************************************************
[Thr 1096337744] Wed Apr 29 11:05:40 2009
[Thr 1096337744] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1096337744] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1096337744] JLaunchISetClusterId: set cluster id 303266050
[Thr 1096337744] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1096337744] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 1119500624] Wed Apr 29 11:06:00 2009
[Thr 1119500624] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 1119500624] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 1119500624] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 1119500624] **********************************************************************
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 1119500624] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 1119500624] JLaunchCloseProgram: good bye (exitcode = -11113)
file: security.0.log
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/system/security.log]/>
<!PATTERN[security.log]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 5, 10485760]/>
<!PREVIOUSFILE[security.4.log]/>
<!NEXTFILE[security.1.log]/>
<!LOGHEADER[END]/>
#1.5^H#002268378E4200230000000000001E47000468B3C171167E#1241021160691#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_34##0#0#Error#1#com.sap.security.core.persistence#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=******** lang=EN receiverid=master sysnr=$$ client=001 poolmaxsize=10 user=SAPJSF receiverid_guest=master ashost=localhost poolmaxwait=10000 } # #1.5^H#002268378E4200230000000300001E47000468B3C1711C36#1241021160692#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_34##0#0#Error#1#com.sap.security.core.persistence#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Password logon no longer possible - too many failed attempts# #1.5^H#002268378E4200230000000500001E47000468B3C1711F80#1241021160692#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_34##0#0#Fatal#1#com.sap.security.core.persistence#Java#Initialization of ABAP data source () failed: "". This message is critical if it appears during the startup of the AS Java.##Initialization of ABAP data source () failed: "". This message is critical if it appears during the startup of the AS Java.#2#com.sap.security.core.persistence.datasource.imp.R3Persistence#Password logon no longer possible - too many failed attempts#
#1.5^H#002268378E4200230000000A00001E47000468B3C1712696#1241021160695#/System/Security/Usermanagement##com.sap.security.core.server.ume.service.UMEServiceFrame#######SAPEngine_System_Thread[impl:5]_34##0#0#Fatal#1#com.sap.security.core.server.ume.service.UMEServiceFrame#Plain#Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts###
Hi Udev,
Thanks for the response. You were correct about SAPJSF.
I also found the thread: J2EE server nodes "Start of UME service failed" after HW change
The person wrote: With the configtool, I have reset the password on property ume.r3.connection.master.passwd to the SAPJSF password for the service com.sap.security.core.ume.service.
I found that the config tool was stored in: /usr/sap/KXE/DVEBMGS30/j2ee/configtool
Like you said, the SAPJSF ID was locked on the ABAP side - so - I unlocked it.
I also followed the step from the old thread mentioned above.
Now, I get the following with the the execution of jcmon
Idx | Name | PID | State | Error | Restart |
--- | |||||
0 | dispatcher | 9626 | Running | 0 | yes |
1 | server0 | 12277 | Running | 4 | yes |
2 | SDM | 9628 | Running | 0 | yes |
-
So, now all is running well
TIA
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
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.