cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE Engine Stopped with Error 11113

Former Member
0 Kudos

Hi All,

After I changed some values in the Portal UME to connect to ECC 6.0, after the restart of cluster the J2EE is not coming up and getting stopped with Error 11113.

I have changed the Datasource to ABAP and tried resetting the values in Configtool as per the previous threads in the forum but could not get my J2EE engine up.

Please find the last some last line of "std_server0.out" file:

-


-


stdout/stderr redirect

-


node name : server0

pid : 3456

system name : EP7

system nr. : 01

started at : Wed May 07 12:35:19 2008

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

[Thr 5340] MtxInit: -2 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

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading: LogManager ... 562 ms.

Loading: PoolManager ... 16 ms.

Loading: ApplicationThreadManager ... 203 ms.

Loading: ThreadManager ... 62 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... 234 ms.

Loading: LockingManager ... 250 ms.

Loading: ConfigurationManager ... 2203 ms.

Loading: LicensingManager ... 31 ms.

Loading: CacheManager ... 172 ms.

Loading: ServiceManager ...

Loading services.:

Service memory started. (31 ms).

Service runtimeinfo started. (172 ms).

Service cafeucc~api started. (281 ms).

Service cross started. (219 ms).

Service timeout started. (156 ms).

Service file started. (500 ms).

Service userstore started. (78 ms).

Service jmx_notification started. (94 ms).

Service trex.service started. (156 ms).

Service p4 started. (282 ms).

Service classpath_resolver started. (46 ms).

Service log_configurator started. (7172 ms).

Service locking started. (0 ms).

Service naming started. (515 ms).

Service http started. (703 ms).

Service javamail started. (297 ms).

Service failover started. (219 ms).

Service appclient started. (203 ms).

Service ts started. (250 ms).

Service jmsconnector started. (297 ms).

Service licensing started. (32 ms).

Service cafeugpmailcf started. (281 ms).

Service connector started. (531 ms).

Service webservices started. (953 ms).

Service iiop started. (672 ms).

Service deploy started. (20344 ms).

Service MigrationService started. (47 ms).

Service bimmrdeployer started. (16 ms).

Service configuration started. (31 ms).

Service dbpool started. (2453 ms).

May 7, 2008 12:35:57 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: 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: "'password' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

receiverid_guest=master

poolmaxwait=10000

client=800

user=sapuser

sysnr=02

poolmaxsize=10

ashost=SAP4

receiverid=master

}

".

May 7, 2008 12:35:57 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

May 7, 2008 12:35:57 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_78] Fatal:

May 7, 2008 12:35:57 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_78] 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: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

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

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

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

Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: 'password' missing

at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)

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

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

... 6 more

com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

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

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

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

Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: 'password' missing

at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)

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

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

... 6 more

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

May 7, 2008 12:35:57 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_78] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

-


Please take a look and help me in resolving this problem. Do let me know you need anymore other logs for analysis ?

Regards,

Srikar

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Srikar,

Did you check this thread.

Cheers,

Sandeep Tudumu

Former Member
0 Kudos

Hi Sandeep,

As per that thread I have done the settings and the J2EE Engine is started without any errors, but when I try to access portal the screen is coming in German Langugae and not getting logged in J2EE_ADMIN user.

Can you let me know what would be the issue out here ?

Regards,

Srikar

Former Member
0 Kudos

Srikar,

For your first question.

Check your browser settings.

If you are using, IE, go to tools->Internet options and click on Language button and see if you have English there, else add the language.

With regards to not able to logon using J2EE admin

Assign R/3 role "SAP_J2EE_ADMIN" to J2EE_Admin.

1. logon to backend system

2. Enter T-Code "SU01"

3. Enter user name "J2EE_ADMIN" then assign role "SAP_J2EE_ADMIN" and save it and try.

Consider rewarding points for handy posts!

Cheers,

Sandeep Tudumu

Former Member
0 Kudos

Hi Sandeep,

For the first problem I have set the default settings to the Guest user in configtool, it solved the problem.

Now for J2EE_ADMIN and role you mentioned is already assigned in the backend. When I try to login to the Portal with the user J2EE_ADMIN, it is just not getting in and even not showing any errors while trying.

Please put some light in this issue.

Regards,

Srikar

Former Member
0 Kudos

Srikar,

Please check these threads,

Cheers,

Sandeep Tudumu

Former Member
0 Kudos

Srikar,

The error message clearly shows that there is some wrong details given in UME Properties.

Check all the properties starting with

ume.r3.connection.master.*

Check SAPJSF - Communication User's password.

Check whether proper client number has been given or not.

Check other UME properties and let me know if you face any issues.

Regards,

Karthick Eswaran

Former Member
0 Kudos

Hi Karthik,

I have checked all the UME properties and are fine. I am trying to connect to ECC 6.0 Clnt 800 with Communication user I created called "portaluser" and the pwd along with system number and application host.

I tried giving all the details in Configtool > Ume properties but again the same problem J2EE is getting stopped with the same error.

About the SAPJSF user, it has been created while installation as a Dailog user in the EP system. I logged into the EP system and checked that in SU01. It there but not as a communication user but as a Dialog user.

Can you let me know what could be the issue ?

Regards,

Srikar

Edited by: Srikar Vankadaru on May 8, 2008 7:59 PM

Former Member
0 Kudos

Hi All,

For the time being after setting up some UME configuration, the J2EE engine could start, but I have some problem logging into the portal, I will start a new thread for that.

Thanks for all the inputs.

Cheers,

Srikar