Skip to Content
0
Former Member
May 12, 2013 at 12:09 AM

Start of UME service failed -- Connect to SAP gateway failed

452 Views

Hi all,

I have used the ABAP stack of an installed Solution Manager to install Gateway on that stack. The installation of the Gateway Add-ons seemed to be fine. Finally, the installation was completed providing the message that Gateway is active now.

Out of the blue and a day later, I could not connect to Solution Manager anymore. I am not aware that I have changed anything that might caused the problem.

I found the following error message in this file C:\usr\sap\SM1\DVEBMGS00\work\std_server0.out:

". This message is critical if it appears during the startup of the AS Java.

May 11, 2013 8:40:46 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_70] Fatal:

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

I tried to restart Solution Manager but the Java stack failed to restart completely. The J2EE Dispatcher and Java server processes remain in the status 'starting framework'. And after a long time, the server0 Java Server just dies resulting in the status 'stopped' and the exit code '-11113 (Core service or additional service start fails; "HaltOnAddtionalServiceFailure=true" (service Manager)'

What is the purpose of the UME service?

I found the following error message in this file C:\usr\sap\SM1\DVEBMGS00\work\std_server0.out:

Loading: ServiceManager ...

Loading services.:

Service memory started. (31 ms).

Service cross started. (31 ms).

Service file started. (125 ms).

Service runtimeinfo started. (47 ms).

Service timeout started. (78 ms).

Service trex.service started. (47 ms).

Service userstore started. (62 ms).

Service jmx_notification started. (32 ms).

Service p4 started. (109 ms).

Service classpath_resolver started. (15 ms).

10.400: [GC 10.400: [ParNew: 412136K->16773K(512000K), 0.0427963 secs] 412136K->16773K(1994752K), 0.0429939 secs] [Times: user=0.11 sys=0.03, real=0.05 secs]

Service log_configurator started. (4681 ms).

Service locking started. (16 ms).

Service naming started. (343 ms).

Service http started. (327 ms).

Service failover started. (16 ms).

Service appclient started. (47 ms).

Service jmsconnector started. (78 ms).

Service licensing started. (187 ms).

Service javamail started. (202 ms).

Service ts started. (140 ms).

14.578: [GC 14.578: [ParNew: 426373K->26089K(512000K), 0.0579072 secs] 426373K->26089K(1994752K), 0.0580584 secs] [Times: user=0.13 sys=0.02, real=0.05 secs]

Service connector started. (266 ms).

Service iiop started. (234 ms).

Service deploy started. (6990 ms).

Service configuration started. (16 ms).

Service MigrationService started. (47 ms).

Service dbpool started. (1031 ms).

Service UT started. (16 ms).

Service tc~lm~nzdm~crrsrv started. (374 ms).

Service bi~mmr~deployer started. (0 ms).

May 11, 2013 8:40:46 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_70] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

I have some more error message in C:\usr\sap\SM1\DVEBMGS00\work\std_bootstrap_ID3411400.o00:

(CompilerOracle read from file C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] Sat May 11 23:41:58 2013

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] Sat May 11 23:41:59 2013

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

[Thr 5100] *** ERROR => JsfGetShmVmci: check failed: sRefs.statAccess > SFI_SMA_NOTINIT [jsfxxsproc.c 439]

And this is the log dev_server0 log file:

I am not confident that the JVM parameter configuration is setup correctly.

You will find the following line. Is that an issue?
[Thr 4552] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\SM1\DVEBMGS00\exe\jvmx.jar

Why is the system trying to access this jar file jvmx.jar in that directory 'C:\usr\sap\SM1\DVEBMGS00\exe'? I can find this JAR file under some sub-directories of 'C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4'. Why is the system not using the sapjvm_4 libs? JAVA_HOME is 'C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4'.

---------------------------------------------------

trc file: "dev_server0", trc level: 1, release: "720"

---------------------------------------------------

node name : ID3411450

pid : 5572

system name : SM1

system nr. : 00

started at : Sat May 11 23:42:03 2013

arguments :

arg[00] : C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe

arg[01] : pf=\\WEDOIT-HOST\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WEDOIT-HOST

arg[02] : -DSAPINFO=SM1_00_server

arg[03] : pf=\\WEDOIT-HOST\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WEDOIT-HOST

arg[04] : -DSAPSTART=1

arg[05] : -DCONNECT_PORT=49297

arg[06] : -DSAPSYSTEM=00

arg[07] : -DSAPSYSTEMNAME=SM1

arg[08] : -DSAPMYNAME=WEDOIT-HOST_SM1_00

arg[09] : -DSAPPROFILE=\\WEDOIT-HOST\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WEDOIT-HOST

arg[10] : -DFRFC_FALLBACK=ON

arg[11] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************

Used property files

-> files [00] : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties

**********************************************************************

**********************************************************************

Bootstrap nodes

-> [00] bootstrap : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties

-> [01] bootstrap_ID3411400 : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties

-> [02] bootstrap_ID3411450 : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties

**********************************************************************

**********************************************************************

Worker nodes

-> [00] ID3411400 : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties

-> [01] ID3411450 : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties

**********************************************************************

**********************************************************************

JStartupReadInstanceProperties: read instance properties [C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties]

-> ms host : WEDOIT-HOST

-> ms port : 3901

-> OS libs : C:\usr\sap\SM1\DVEBMGS00\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

[Thr 4552] Sat May 11 23:42:03 2013

[Thr 4552] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 4552] JLaunchRequestQueueInit: create pipe listener thread

[Thr 2004] JLaunchRequestFunc: Thread 2004 started as listener thread for np messages.

[Thr 5524] WaitSyncSemThread: Thread 5524 started as semaphore monitor thread.

[Thr 4552] JLaunchInitSignalHandling: signal handling is disabled

[Thr 4552] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

[Thr 4552] MPI: dynamic quotas disabled.

[Thr 4552] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

[Thr 4552] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)

[Thr 4552] CCMS uses Shared Memory Key 73 for monitoring.

[Thr 4552] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

[Thr 4552] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

[Thr 4552] CCMS: CCMS Monitoring Initialization finished, rc=0.

[Thr 4552] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\SM1\DVEBMGS00\exe\jvmx.jar

**********************************************************************

JStartupIReadSection: read node properties [ID3411450]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4

-> java parameters : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee

-> java vm version : 4.1.024 1.6-b04

-> java vm vendor : SAP Java Server VM (SAP AG)

-> java vm type : server

-> java vm cpu : amd64

-> heap size : 2048M

-> init heap size : 2048M

-> stack size : 2M

-> root path : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\server0

-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> OS libs path : C:\usr\sap\SM1\DVEBMGS00\j2ee\os_libs

-> main class : com.sap.engine.boot.Start

-> framework class : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path : C:\usr\sap\SM1\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\SM1\DVEBMGS00\exe\jvmx.jar

-> shutdown class : com.sap.engine.boot.Start

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 50021

-> shutdown timeout : 120 sec.

**********************************************************************

[Thr 4552] JLaunchISetDebugMode: set debug mode [no]

[Thr 5656] JLaunchIStartFunc: Thread 5656 started as Java VM thread.

**********************************************************************

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 2097152 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: vfprintf

-> arg[ 3]: -XX:MaxNewSize=600M

-> arg[ 4]: -XX:NewSize=600M

-> arg[ 5]: -XX:MaxPermSize=512M

-> arg[ 6]: -XX:PermSize=512M

-> arg[ 7]: -XX:+UseConcMarkSweepGC

-> arg[ 8]: -XX:+DisableExplicitGC

-> arg[ 9]: -XX:TargetSurvivorRatio=90

-> arg[ 10]: -XX:SurvivorRatio=4

-> arg[ 11]: -XX:+PrintGCDetails

-> arg[ 12]: -XX:+PrintGCTimeStamps

-> arg[ 13]: -verbose:gc

-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1

-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof

-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError

-> arg[ 17]: -Djco.jarm=1

-> arg[ 18]: -Djava.awt.headless=true

-> arg[ 19]: -Djava.security.policy=./java.policy

-> arg[ 20]: -Djava.security.egd=file:/dev/urandom

-> arg[ 21]: -Dsun.io.useCanonCaches=false

-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee

-> arg[ 27]: -Dsys.global.dir=C:\usr\sap\SM1\SYS\global

-> arg[ 28]: -Dapplication.home=C:\usr\sap\SM1\DVEBMGS00\exe

-> arg[ 29]: -Djava.class.path=C:\usr\sap\SM1\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\SM1\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> arg[ 30]: -Djava.library.path=C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\jre\bin\server;C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\jre\bin;C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\bin;C:\usr\sap\SM1\DVEBMGS00\j2ee\os_libs;C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\jre\bin\server;C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\jre\bin;C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\bin;C:\usr\sap\SM1\DVEBMGS00\j2ee\os_libs;C:\usr\sap\SM1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Amazon\cfn-bootstrap\;C:\sap_downloads\SAPCAR\SAPCAR.EXE;C:\usr\sap\SM1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SM1\bin;C:\sapdb\clients\SM1\pgm;C:\sapdb\programs\bin

-> arg[ 31]: -Dmemory.manager=2048M

-> arg[ 32]: -Xmx2048M

-> arg[ 33]: -Xms2048M

-> arg[ 34]: -Xss2M

-> arg[ 35]: -DLoadBalanceRestricted=no

-> arg[ 36]: -Djstartup.mode=JCONTROL

-> arg[ 37]: -Djstartup.ownProcessId=5572

-> arg[ 38]: -Djstartup.ownHardwareId=C0758871570

-> arg[ 39]: -Djstartup.whoami=server

-> arg[ 40]: -Djstartup.debuggable=no

-> arg[ 41]: -Xjvmx

-> arg[ 42]: -XsapSystem=00

-> arg[ 43]: -XmonGcCallback

-> arg[ 44]: -DSAPINFO=SM1_00_server

-> arg[ 45]: -DSAPSTART=1

-> arg[ 46]: -DCONNECT_PORT=49297

-> arg[ 47]: -DSAPSYSTEM=00

-> arg[ 48]: -DSAPSYSTEMNAME=SM1

-> arg[ 49]: -DSAPMYNAME=WEDOIT-HOST_SM1_00

-> arg[ 50]: -DSAPPROFILE=\\WEDOIT-HOST\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WEDOIT-HOST

-> arg[ 51]: -DFRFC_FALLBACK=ON

-> arg[ 52]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 53]: -DSAPSTARTUP=1

-> arg[ 54]: -DSAPSYSTEM=00

-> arg[ 55]: -DSAPSYSTEMNAME=SM1

-> arg[ 56]: -DSAPMYNAME=WEDOIT-HOST_SM1_00

-> arg[ 57]: -DSAPDBHOST=WEDOIT-HOST

-> arg[ 58]: -Dj2ee.dbhost=WEDOIT-HOST

**********************************************************************

(CompilerOracle read from file C:\usr\sap\SM1\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)

[Thr 5656] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [server0]

**********************************************************************

[Thr 5960] Sat May 11 23:42:05 2013

[Thr 5960] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes

Sat May 11 23:42:06 2013

2.792: [GC 2.792: [ParNew: 409600K->2537K(512000K), 0.0122479 secs] 409600K->2537K(1994752K), 0.0123789 secs] [Times: user=0.06 sys=0.00, real=0.02 secs]

[Thr 5960] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework

[Thr 5960] JLaunchISetClusterId: set cluster id 3411450

[Thr 5960] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 5960] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

Sat May 11 23:42:12 2013

9.574: [GC 9.574: [ParNew: 412137K->17894K(512000K), 0.0448551 secs] 412137K->17894K(1994752K), 0.0450951 secs] [Times: user=0.13 sys=0.01, real=0.05 secs]

Sat May 11 23:42:16 2013

13.524: [GC 13.524: [ParNew: 427494K->27681K(512000K), 0.0499108 secs] 427494K->27681K(1994752K), 0.0500843 secs] [Times: user=0.19 sys=0.00, real=0.05 secs]

[Thr 5388] Sat May 11 23:42:19 2013

[Thr 5388] JHVM_RegisterNatives: com.sap.mw.rfc.driver.CpicDriver

Sat May 11 23:43:19 2013

Heap

par new generation reserved 614400K, committed 614400K, used 129347K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)

eden space 409600K, 24% used [0x000000007fff0000, 0x0000000086338758, 0x0000000098ff0000)

from space 102400K, 27% used [0x000000009f3f0000, 0x00000000a0ef8518, 0x00000000a57f0000)

to space 102400K, 0% used [0x0000000098ff0000, 0x0000000098ff0000, 0x000000009f3f0000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)

concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 35551K [0x00000000ffff0000, 0x000000011fff0000, 0x000000011fff0000)

[Thr 5836] Sat May 11 23:43:20 2013

[Thr 5836] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 5836] **********************************************************************

[Thr 5836] *** ERROR => The Java VM terminated with a non-zero exit code.

[Thr 5836] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'

[Thr 5836] *** for additional information and trouble shooting.

[Thr 5836] **********************************************************************

[Thr 5836] JLaunchCloseProgram: good bye (exitcode = -11113)

Host and system details:

  • I have installed an ERP system and Solution Manager on the same Windows box (just for demo)
  • The host is Amazon EC2 instance running Windows 2008R2 SP1 Server 64 bit (total memory 15 GB and Processing Power 8 ECUs) .
  • The ERP system is ERP 6.0 Support Release 3, MaxDB 7.8, Central System.
  • The Solution Manager 7.1 Support Release 1, MaxDB 7.8, Central System.
  • Gateway 2.0 on the top of Solution Manager
  • SAP MaxDB version 7.8.02.26, the ERP and Solution Manager have their own DB.

Many thanks for your help!

Regards,

Andreas