cancel
Showing results for 
Search instead for 
Did you mean: 

"Start of UME Failed" adding more java servers

Former Member
0 Kudos

We installed an Abap+J2EE Ntw04s system in

MSCS.

On node A we installed the Primary As

(Abap+Java), on the node B we installed a

Secondary As (Abap+Java).

On the Primary As we added further 4 java

servers. These java servers are started

successufully and are working fine.

On the Secondary As we try to add further 4

java servers but we noticed thay are not

started.

We see this error into the st_serverx.out log

file:

" 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: null

ume.db.connection_pool_type=SAP/BC_UM

E

ume.db.connection_pool.j2ee.xatransac

tions_used=false

ume.db.connection_pool.j2ee.is_unicod

e=false

ume.db.connection_pool.j2ee.oracle_na

tive_driver_used=false: (No text available)

at

com.sap.security.core.server.ume.service.UMESer

viceFrame.start(UMEServiceFrame.java:398)

at

com.sap.engine.frame.ApplicationFrameAdaptor.st

art(ApplicationFrameAdaptor.java:31)

at

com.sap.engine.core.service630.container.Servic

eRunner.startApplicationServiceFrame

(ServiceRunner.java:214)

at

com.sap.engine.core.service630.container.Servic

eRunner.run(ServiceRunner.java:144)

at

com.sap.engine.frame.core.thread.Task.run

(Task.java:64)

at

com.sap.engine.core.thread.impl5.SingleThread.e

xecute(SingleThread.java:81)

at

com.sap.engine.core.thread.impl5.SingleThread.r

un(SingleThread.java:152)

Caused by:

com.sap.security.core.persistence.datasource.Pe

rsistenceException: null

ume.db.connection_pool_type=SAP/BC_UM

E

ume.db.connection_pool.j2ee.xatransac

tions_used=false

ume.db.connection_pool.j2ee.is_unicod

e=false

ume.db.connection_pool.j2ee.oracle_na

tive_driver_used=false: (No text available)

at

com.sap.security.core.persistence.datasource.im

p.DataBasePersistence.init

(DataBasePersistence.java:887)

at

com.sap.security.core.persistence.imp.Principal

DatabagFactoryInstance.<init>

(PrincipalDatabagFactoryInstance.java:445)

at

com.sap.security.core.persistence.imp.Principal

DatabagFactory.newInstance

(PrincipalDatabagFactory.java:164)

at

com.sap.security.core.persistence.imp.Principal

DatabagFactory.getInstance

(PrincipalDatabagFactory.java:117)

at

com.sap.security.core.persistence.imp.Principal

DatabagFactory.getInstance

(PrincipalDatabagFactory.java:63)

at

com.sap.security.core.InternalUMFactory.initial

izeUME(InternalUMFactory.java:221)

at

com.sap.security.core.server.ume.service.UMESer

viceFrame.start(UMEServiceFrame.java:287)"

Due to this error none of the 5 java server,

including the default server0, of this

Secondary As is started.

We removed the further java servers added,

leaving the default server0 and at restart we

see it's able to start normally.

We suspect there is some parameter to be

configured, to allow more connections to the

DB by the java servers, but we do not know

which is.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

In config tool you have DBPool.. increase the value.

Config Tool > Server > Services > DBPOOL > sysDS.maximumConnection : Increase the value here..

Hope this solves your problem. If yes, please reward points.

Rgds,

KINO

Answers (0)