cancel
Showing results for 
Search instead for 
Did you mean: 

AS Java won't start ; Exitcode -11113

Former Member
0 Kudos

Hi,

I tried to start my Solution Manager system but it got stuck as the server0 from the AS Java couldn't start.

Specs :

Solution Manager 7.1 SP 04

Windows Server 2012R2

And here below is the log from std_server0.out

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

stdout/stderr redirect

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

node name   : server0

pid         : 5276

system name : S67

system nr.  : 00

started at  : Thu Jun 23 17:29:22 2016

[Thr 15836] MtxInit: 10001 0 2

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

SAP J2EE Engine Version 7.02   PatchLevel 115420. is starting...

Loading: LogManager ... 414 ms.

Loading: PoolManager ... 3 ms.

Loading: ApplicationThreadManager ... 98 ms.

Loading: ThreadManager ... 12 ms.

Loading: IpVerificationManager ... 6 ms.

Loading: ClassLoaderManager ... 449 ms.

Loading: ClusterManager ... 2.948: [GC 2.948: [ParNew: 409600K->3111K(512000K), 0.2073368 secs] 409600K->3111K(1994752K), 0.2075700 secs] [Times: user=0.02 sys=0.00, real=0.21 secs]

3.172: [GC 3.172: [ParNew: 412711K->3943K(512000K), 0.1079727 secs] 412711K->3943K(1994752K), 0.1081198 secs] [Times: user=0.02 sys=0.00, real=0.11 secs]

740 ms.

Loading: LockingManager ... 68 ms.

Loading: ConfigurationManager ... 1909 ms.

Loading: LicensingManager ... 43 ms.

Loading: CacheManager ... 70 ms.

Loading: ServiceManager ...

Loading services.:

  Service memory started. (56 ms).

  Service trex.service started. (62 ms).

  Service cross started. (72 ms).

  Service runtimeinfo started. (61 ms).

  Service file started. (78 ms).

  Service timeout started. (71 ms).

  Service jmx_notification started. (13 ms).

  Service userstore started. (9 ms).

  Service p4 started. (86 ms).

  Service classpath_resolver started. (15 ms).

8.874: [GC 8.874: [ParNew: 413543K->20307K(512000K), 0.0194296 secs] 413543K->20307K(1994752K), 0.0196395 secs] [Times: user=0.06 sys=0.00, real=0.02 secs]

8.907: [GC [1 CMS-initial-mark: 0K(1482752K)] 22097K(1994752K), 0.0044346 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

8.912: [CMS-concurrent-mark-start]

8.923: [CMS-concurrent-mark: 0.011/0.011 secs] [Times: user=0.03 sys=0.02, real=0.01 secs]

8.924: [CMS-concurrent-preclean-start]

8.927: [CMS-concurrent-preclean: 0.003/0.003 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

8.927: [CMS-concurrent-abortable-preclean-start]

11.131: [CMS-concurrent-abortable-preclean: 1.173/2.204 secs] [Times: user=6.50 sys=1.13, real=2.20 secs]

11.132: [GC [YG occupancy: 304651 K (512000 K)]11.132: [Rescan (parallel) , 0.0376732 secs]11.170: [weak refs processing, 0.0001326 secs]11.170: [class unloading, 0.0030647 secs]11.173: [scrub symbol table, 0.0042539 secs]11.177: [scrub string table, 0.0007673 secs][1 CMS-remark: 0K(1482752K)] 304651K(1994752K), 0.0471524 secs] [Times: user=0.19 sys=0.00, real=0.05 secs]

11.179: [CMS-concurrent-sweep-start]

11.179: [CMS-concurrent-sweep: 0.000/0.000 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

11.179: [CMS-concurrent-reset-start]

11.183: [CMS-concurrent-reset: 0.004/0.004 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

  Service log_configurator started. (4093 ms).

  Service locking started. (4 ms).

  Service naming started. (199 ms).

  Service appclient started. (20 ms).

11.972: [GC 11.972: [ParNew: 429907K->24062K(512000K), 0.0225082 secs] 429907K->24062K(1994752K), 0.0226803 secs] [Times: user=0.06 sys=0.00, real=0.02 secs]

  Service failover started. (81 ms).

  Service jmsconnector started. (98 ms).

  Service http started. (335 ms).

  Service licensing started. (212 ms).

  Service javamail started. (230 ms).

  Service ts started. (142 ms).

  Service connector started. (103 ms).

  Service iiop started. (110 ms).

  Service deploy started. (7479 ms).

  Service MigrationService started. (18 ms).

  Service configuration started. (10 ms).

  Service dbpool started. (1025 ms).

  Service UT started. (7 ms).

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

Jun 23, 2016 5:29:40 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] 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

LOCATION    CPIC (TCP/IP) on local host FRPARSSM-PCOE with Unicode

ERROR       partner '127.0.0.1:sapgw00' not reached

TIME        Thu Jun 23 17:29:40 2016

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3283

DETAIL      NiPConnect2: 127.0.0.1:3300

SYSTEM CALL connect

ERRNO       10061

ERRNO TEXT  WSAECONNREFUSED: Connection refused

COUNTER     1

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

Jun 23, 2016 5:29:40 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_71] 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

LOCATION    CPIC (TCP/IP) on local host FRPARSSM-PCOE with Unicode

ERROR       partner '127.0.0.1:sapgw00' not reached

TIME        Thu Jun 23 17:29:40 2016

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3283

DETAIL      NiPConnect2: 127.0.0.1:3300

SYSTEM CALL connect

ERRNO       10061

ERRNO TEXT  WSAECONNREFUSED: Connection refused

COUNTER     1

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)

    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:83)

    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

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

LOCATION    CPIC (TCP/IP) on local host FRPARSSM-PCOE with Unicode

ERROR       partner '127.0.0.1:sapgw00' not reached

TIME        Thu Jun 23 17:29:40 2016

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3283

DETAIL      NiPConnect2: 127.0.0.1:3300

SYSTEM CALL connect

ERRNO       10061

ERRNO TEXT  WSAECONNREFUSED: Connection refused

COUNTER     1

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:447)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

    at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)

    ... 6 more

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

LOCATION    CPIC (TCP/IP) on local host FRPARSSM-PCOE with Unicode

ERROR       partner '127.0.0.1:sapgw00' not reached

TIME        Thu Jun 23 17:29:40 2016

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3283

DETAIL      NiPConnect2: 127.0.0.1:3300

SYSTEM CALL connect

ERRNO       10061

ERRNO TEXT  WSAECONNREFUSED: Connection refused

COUNTER     1

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)

    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:83)

    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

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

LOCATION    CPIC (TCP/IP) on local host FRPARSSM-PCOE with Unicode

ERROR       partner '127.0.0.1:sapgw00' not reached

TIME        Thu Jun 23 17:29:40 2016

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3283

DETAIL      NiPConnect2: 127.0.0.1:3300

SYSTEM CALL connect

ERRNO       10061

ERRNO TEXT  WSAECONNREFUSED: Connection refused

COUNTER     1

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:447)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

    at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)

    ... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Jun 23, 2016 5:29:40 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_71] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Heap

par new generation   reserved 614400K, committed 614400K, used 189561K [0x0000000080000000, 0x00000000a5800000, 0x00000000a5800000)

  eden space 409600K,  40% used [0x0000000080000000, 0x000000008a19ebd8, 0x0000000099000000)

  from space 102400K,  23% used [0x0000000099000000, 0x000000009a77f8a0, 0x000000009f400000)

  to   space 102400K,   0% used [0x000000009f400000, 0x000000009f400000, 0x00000000a5800000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a5800000, 0x0000000100000000, 0x0000000100000000)

Metaspace       used 32091K, capacity 34458K, committed 34816K, reserved 292864K

  class space    used 3338K, capacity 3988K, committed 4096K, reserved 262144K

I'm pretty new to Solution Manager (I'm an intern), and I couldn't find much help on the web, one reason may be that the J2EE_ADMIN user is locked but I don't know how to check that nor if that's the reason.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi,

This SAP note might help you.

1707693 - User account not in validity date on localhost: SAP startup issue


Regards

Abhijit

Former Member
0 Kudos

Hi Abhijit,

When I try to use configtool, it seems to fail, it tries to connect for ages to the databse and in the end all I got is this :

Reagan
Advisor
Advisor
0 Kudos

Check whether the database is up and running. Most likely the issue could be with the database. Check the ABAP developer traces (dev_w0) and see what it says.

Answers (2)

Answers (2)

ImtiazKaredia
Active Contributor
0 Kudos
patelyogesh
Active Contributor
0 Kudos

Hello Dimitri,



Error Looks like me is UME related error..


Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Connect to SAP gateway failed


Make sure your SAPJSF user in ABAP system have SAP_BC_JSF_COMMUNICATION role assigned.


You also make sure SAP_BC_JSF_COMMUNICATION role profiles generated.


Regards,

Yogesh