cancel
Showing results for 
Search instead for 
Did you mean: 

Server is not starting after creating a new data source

Former Member
0 Kudos

Hi,

I created a new data source in visual admin. After restart, the server is not starting. I get exitcode = -11113, in the log file.

In the configtool, I could see the datasource details in Global Server configuration ->Services->dbpool,

I copied the original default values for sysDS.aliases, sysDS.dataSourceName, from other environment.

For the sysDS.driverName , I left blank, as other environments didn't have any value.

When I restarted, nobody is able to login, even Administrator. What could've gone wrong ???

Thanks

Tony

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

So after restarting, you are able to connect to config tool but the server is not starting.

what is the output of dev_disp file ?

Thanks!

Answers (1)

Answers (1)

debasissahoo
Active Contributor
0 Kudos

Tony,

Check the blog, if it might help you.

/people/antal.perger/blog/2009/03/19/java-server-startup-problems--11113

Thanks,

Debasis.

Former Member
0 Kudos

Hi,

In my case LDAP is the data source, the blog refers to ABAP as data source. Here is the log file (std_server0.out)


Mar 25, 2009 5:09:57 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_75] 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: null
	ume.db.connection_pool_type=SAP/BC_UME
	ume.db.connection_pool.j2ee.xatransactions_used=false
	ume.db.connection_pool.j2ee.is_unicode=false
	ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
	at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
	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:81)
	at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
	ume.db.connection_pool_type=SAP/BC_UME
	ume.db.connection_pool.j2ee.xatransactions_used=false
	ume.db.connection_pool.j2ee.is_unicode=false
	ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
	at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
	at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
	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:287)
	... 6 more


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_UME
	ume.db.connection_pool.j2ee.xatransactions_used=false
	ume.db.connection_pool.j2ee.is_unicode=false
	ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
	at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
	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:81)
	at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
	ume.db.connection_pool_type=SAP/BC_UME
	ume.db.connection_pool.j2ee.xatransactions_used=false
	ume.db.connection_pool.j2ee.is_unicode=false
	ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
	at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
	at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
	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:287)
	... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Mar 25, 2009 5:09:57 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_75] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
--------------------------------------------------------------------------------
stdout/stderr redirect
--------------------------------------------------------------------------------
node name   : server0
pid         : 4856
system name : EPT
system nr.  : 01
started at  : Wed Mar 25 17:09:58 2009

Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 6468] MtxInit: 10001 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto

SAP J2EE Engine Version 7.00   PatchLevel 112614.44 is starting...

Loading: LogManager ... 641 ms. 
Loading: PoolManager ... 15 ms. 
Loading: ApplicationThreadManager ... 110 ms. 
Loading: ThreadManager ... 31 ms. 
Loading: IpVerificationManager ... 0 ms. 
Loading: ClassLoaderManager ... 31 ms. 
Loading: ClusterManager ... 266 ms. 
Loading: LockingManager ... 109 ms. 
Loading: ConfigurationManager ... 6422 ms. 
Loading: LicensingManager ... 62 ms. 
Loading: CacheManager ... 469 ms. 
Loading: ServiceManager ...