cancel
Showing results for 
Search instead for 
Did you mean: 

j2ee server stopped, exitcode = -11113 after changing client to 800

Former Member
0 Kudos

Hi

-


trc file: "D:\usr\sap\DEV\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"

-


node name : ID7053350

pid : 4892

system name : DEV

system nr. : 00

started at : Tue Sep 07 17:31:25 2010

arguments :

arg[00] : D:\usr\sap\DEV\DVEBMGS00\exe\jlaunch.exe

arg[01] : pf=D:\usr\sap\DEV\SYS\profile\DEV_DVEBMGS00_vijaydev

arg[02] : -DSAPINFO=DEV_00_server

arg[03] : pf=D:\usr\sap\DEV\SYS\profile\DEV_DVEBMGS00_vijaydev

arg[04] : -DSAPSTART=1

arg[05] : -DCONNECT_PORT=1868

arg[06] : -DSAPSYSTEM=00

arg[07] : -DSAPSYSTEMNAME=DEV

arg[08] : -DSAPMYNAME=vijaydev_DEV_00

arg[09] : -DSAPPROFILE=D:\usr\sap\DEV\SYS\profile\DEV_DVEBMGS00_vijaydev

arg[10] : -DFRFC_FALLBACK=ON

arg[11] : -DFRFC_FALLBACK_HOST=localhost

[Thr 2176] Tue Sep 07 17:31:25 2010

[Thr 2176] *** WARNING => INFO: Unknown property [instance.box.number=DEVDVEBMGS00vijaydev] [jstartxx.c 841]

[Thr 2176] *** WARNING => INFO: Unknown property [instance.en.host=vijaydev] [jstartxx.c 841]

[Thr 2176] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]

[Thr 2176] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

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

JStartupReadInstanceProperties: read instance properties [D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties]

-> ms host : vijaydev

-> ms port : 3901

-> OS libs : D:\usr\sap\DEV\DVEBMGS00\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

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

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

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

Instance properties

-> ms host : vijaydev

-> ms port : 3901

-> os libs : D:\usr\sap\DEV\DVEBMGS00\j2ee\os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

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

-> [01] bootstrap_ID7053300 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

-> [02] bootstrap_ID7053350 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

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

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

Worker nodes

-> [00] ID7053300 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

-> [01] ID7053350 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

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

[Thr 2176] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 2176] JLaunchRequestQueueInit: create pipe listener thread

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

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

[Thr 2176] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 2176] CPIC (version=700.2006.09.13)

[Thr 2176] [Node: server0] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_17

[Thr 2176] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\DEV\DVEBMGS00\exe\jvmx.jar

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

JStartupIReadSection: read node properties [ID7053350]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : C:\j2sdk1.4.2_17

-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-> java vm version : 1.4.2_17-b06

-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : x86

-> heap size : 1024M

-> init heap size : 1024M

-> root path : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\server0

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

-> OS libs path : D:\usr\sap\DEV\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 : D:\usr\sap\DEV\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\DEV\DVEBMGS00\exe\jvmx.jar

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

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 50021

-> shutdown timeout : 120000

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

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

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

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

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 262144 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: vfprintf

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

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

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

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

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

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

-> arg[ 9]: -XX:MaxPermSize=256M

-> arg[ 10]: -XX:PermSize=256M

-> arg[ 11]: -XX:NewSize=171M

-> arg[ 12]: -XX:MaxNewSize=171M

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

-> arg[ 14]: -verbose:gc

-> arg[ 15]: -Xloggc:GC.log

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

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

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

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

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

-> arg[ 21]: -XX:SurvivorRatio=2

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

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

-> arg[ 24]: -Dsys.global.dir=D:\usr\sap\DEV\SYS\global

-> arg[ 25]: -Dapplication.home=D:\usr\sap\DEV\DVEBMGS00\exe

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

-> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_17\jre\bin\server;C:\j2sdk1.4.2_17\jre\bin;C:\j2sdk1.4.2_17\bin;D:\usr\sap\DEV\DVEBMGS00\j2ee\os_libs;D:\oracle\DEV\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_17\bin;C:\Program Files\Intel\DMIX;D:\usr\sap\DEV\SYS\exe\uc\NTI386

-> arg[ 28]: -Dmemory.manager=1024M

-> arg[ 29]: -Xmx1024M

-> arg[ 30]: -Xms1024M

-> arg[ 31]: -DLoadBalanceRestricted=no

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

-> arg[ 33]: -Djstartup.ownProcessId=4892

-> arg[ 34]: -Djstartup.ownHardwareId=H2122342918

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

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

-> arg[ 37]: -DSAPINFO=DEV_00_server

-> arg[ 38]: -DSAPSTART=1

-> arg[ 39]: -DCONNECT_PORT=1868

-> arg[ 40]: -DSAPSYSTEM=00

-> arg[ 41]: -DSAPSYSTEMNAME=DEV

-> arg[ 42]: -DSAPMYNAME=vijaydev_DEV_00

-> arg[ 43]: -DSAPPROFILE=D:\usr\sap\DEV\SYS\profile\DEV_DVEBMGS00_vijaydev

-> arg[ 44]: -DFRFC_FALLBACK=ON

-> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 46]: -DSAPSTARTUP=1

-> arg[ 47]: -DSAPSYSTEM=00

-> arg[ 48]: -DSAPSYSTEMNAME=DEV

-> arg[ 49]: -DSAPMYNAME=vijaydev_DEV_00

-> arg[ 50]: -DSAPDBHOST=vijaydev

-> arg[ 51]: -Dj2ee.dbhost=vijaydev

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

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

[Thr 2044] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [server0]

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

[Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 5836] Tue Sep 07 17:31:26 2010

[Thr 5836] JLaunchISetClusterId: set cluster id 7053350

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

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

[Thr 4084] Tue Sep 07 17:31:34 2010

[Thr 4084] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 4880] Tue Sep 07 17:31:35 2010

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

[Thr 4880] **********************************************************************

      • ERROR => The Java VM terminated with a non-zero exit code.

      • Please see SAP Note 943602 , section 'J2EE Engine exit codes'

      • for additional information and trouble shooting.

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

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

Accepted Solutions (1)

Accepted Solutions (1)

thunder_feng
Active Participant
0 Kudos

Hi Hari

Just as expected, current the UME service is failing to startup after you changed the client.

Please look at the following "Caused by: "

com.sap.security.core.persistence.datasource.PersistenceException: 'password' missing

It means the password is not being set correctly, please check the following UME properties and make sure all of them are being

set correctly:

ume.r3.connection.master.user

ume.r3.connection.master.passwd <--- this must be set, and the value is the logon password of ume.r3.connection.master.user

ume.r3.connection.master.ashost

ume.r3.connection.master.sysnr

ume.r3.connection.master.client

you can refer to the folloiwng link about how to edit the UME Properties

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/content.htm

and also this link should be helpful for you:

Offline Configuration of the UME for AS ABAP

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/45/1bbdccc7850064e10000000a1553f7/frameset.htm

Best Regards,

Thunder

Edited by: Thunder Feng on Sep 10, 2010 1:21 PM

Former Member
0 Kudos

Hi i set usertype(master user) SAPJSF as "system" type?

is it ok?

Former Member
0 Kudos

Hi,

Ya its fine. But you have to maintain the pwd correctly in the secure store using the config tool.

Regards,

Vamshi.

Former Member
0 Kudos

Hi

I did not change the password in secure store , where I changed in INSTANCE>SERVER>SERVICES--->com.sap.security.core.ume.service - ume.r3.connection.master.passwd

Another thing after changing client did not set the pwd of J2EE_GUEST in configtool, dont find option for that.

even for j2ee_admin..but one thing the pwd is same as 001 clients

Still the error message as same as..

-


Sep 10, 2010 5:44:14 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_68] 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.": "{

lang=EN

receiverid=master

sysnr=$$

client=800

poolmaxsize=100

user=SAPJSF

receiverid_guest=master

ashost=localhost

poolmaxwait=10000

}

".

Sep 10, 2010 5:44:14 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_68] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

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

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'password' missing

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

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

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

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

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

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

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

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

... 6 more

thunder_feng
Active Participant
0 Kudos

Hi Hari

The password must be set via configtool, refer to this:

how to edit the UME Properties

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/content.htm

Best Regards,

Thunder

Former Member
0 Kudos

Hi,

The pwd for SAPJSF and J2EE_ADMIN should be changed in the secure store of config tool not in the ume properties.

Regards,

Vamshi.

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Hari,

I also faced this issue several times.

But usually one faces this issue either after an upgrade from NW04 to NW04s which is solved in the note 942050.

Secondly, user SAPJSF is locked which can be unlocked from ABAP side su01.

Thirdly, due to JVM parameter which are needed to be set for 64 bit systems. There is a note for the same also. Right now i am not able to recall the number of the same. but you can try on the SMP and you can easily find the same by searching aroung Java parameters for 64bit.

Do let us know if issue gets resolved.

Cheers!!!

ElNino

thunder_feng
Active Participant
0 Kudos

Hi Hari

the exitcode = -11113 generally some core service failed, and you can find more details from the corresponding

std_server0.out log file under the same folder with dev_server0.

So please check the std_server0.out and check what is the error there.

Regarding chaning the backend client of your java system, please refer to the following link and notes, then you will be clear about what you need to do:

http://help.sap.com/saphelp_nw70/helpdata/EN/db/8b9b801df84aaaa76bdbcbc0b9725f/frameset.htm

note 937323 Changing Production Client in an ABAP+Java System

note 552711 FAQ Client Copy

Thanks

Thunder

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

What do you means by after changing to client 800 ? Have you changed UME of Java ?

Thanks

Sunny

Former Member
0 Kudos

Hi

Yes, in UME- System administration changed client 001 to 800 and SAPJSF password to new password which is reset in 800

UserId type is System.

sunny_pahuja2
Active Contributor
0 Kudos

Hi ,

while changing UME from client 001 to other client, make sure that you should do the user master client copy from client 001 to other client in your case it is client 800. As initially all Java users will be created in client 001 only. So, you have to do user master copy from client 001 to client 800.

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny,

But it is IDES server, I beleive there is no need of client copy. however I have given all SAP Roles which are there in client 001 and applied in 800 client

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

SAPJSF is not only the user which you need to run Java stack. In config tool, you generally use administrator/J2ee_admin user in secure storage and that user always present in client 001 initially after installation. So you have to do client copy from client 001 with user master.

Thanks

Sunny

Former Member
0 Kudos

Hi

Even I tried to assign all the j2ee role to J2ee_admin user

However I tried to revert the settings that in offline config tool..I have tried to change client 001..and started SAP server..but still J2ee server is not up?

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Could you please paste fresh std_Server and default trace log ?

Thanks

Sunny

Former Member
0 Kudos

Hi,

I hope you have done a client copy for user master from 001. Then one more thing you have to do i.e generate the profile for the role SAP_BC_JSF_COMMUNICATION and assign it to SAPJSF.

Also if you have changed the pwd for the users SAPJSF and J2EE_ADMIN maintan them in the secure store area using the config tool.

If still you face problem paste the security.log and server0.log file.

Regards,

Vamshi.

Former Member
0 Kudos

Hi Hari,

Can you please check the user J2EE_GUEST in client 800 and whether its available or not?

Once I faced the similar issue and it was due to the user J2EE_GUEST. The password and credentials for the user should be same as 001 client.

Please try with this and it may fix your issue.

Thanks,

Jagadish

Former Member
0 Kudos

Hi,

The return code --11113 usually occurs when the J2EE engine is not able to connect to the database with the users SAPJSF and J2EE_GUEST.

Make sure that the users SAPJSF and J2EE_GUEST are available and also not locked in client 800 and the new password for the J2EE_ADMIN has been maintained in the secure store in the config tool.

Regards,

Varadharajan M

Former Member
0 Kudos

The latest trace file of std_server0.out is

-


-


stdout/stderr redirect

-


node name : server0

pid : 1960

system name : DEV

system nr. : 00

started at : Fri Sep 10 16:38:48 2010

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

[Thr 5788] 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

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 is starting...

Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect

Loading: LogManager ... 438 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 156 ms.

Loading: ThreadManager ... 16 ms.

Loading: IpVerificationManager ... 0 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... 344 ms.

Loading: LockingManager ... 47 ms.

Loading: ConfigurationManager ... 2438 ms.

Loading: LicensingManager ... 31 ms.

Loading: CacheManager ... 234 ms.

Loading: ServiceManager ...

Loading services.:

Service userstore started. (16 ms).

Service DQE started. (0 ms).

Service cafeuodi~mnuacc started. (0 ms).

Service memory started. (93 ms).

Service cafeucc~api started. (0 ms).

Service cross started. (16 ms).

Service file started. (125 ms).

Service jmx_notification started. (47 ms).

Service runtimeinfo started. (0 ms).

Service timeout started. (109 ms).

Service trex.service started. (109 ms).

Service p4 started. (172 ms).

Service classpath_resolver started. (15 ms).

Service log_configurator started. (2219 ms).

Service locking started. (0 ms).

Service http started. (250 ms).

Service naming started. (407 ms).

Service failover started. (47 ms).

Service appclient started. (47 ms).

Service ts started. (110 ms).

Service javamail started. (94 ms).

Service licensing started. (16 ms).

Service jmsconnector started. (125 ms).

Service connector started. (156 ms).

Service webservices started. (328 ms).

Service iiop started. (625 ms).

Service deploy started. (5125 ms).

Service MigrationService started. (16 ms).

Service bimmrdeployer started. (16 ms).

Service configuration started. (32 ms).

Service dbpool started. (610 ms).

Service cafeugpmailcf started. (32 ms).

Sep 10, 2010 4:39:02 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_68] 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.": "{

lang=EN

receiverid=master

sysnr=$$

client=800

poolmaxsize=100

user=SAPJSF

receiverid_guest=master

ashost=localhost

poolmaxwait=10000

}

".

Sep 10, 2010 4:39:02 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_68] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

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

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'password' missing

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

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

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

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

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

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

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

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

... 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:372)

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'password' missing

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

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

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

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

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

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

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

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

... 6 more

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

Sep 10, 2010 4:39:02 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_68] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Former Member
0 Kudos

The log of dev_server0

-


[Thr 5788] Fri Sep 10 16:38:48 2010

[Thr 5788] *** WARNING => INFO: Unknown property [instance.box.number=DEVDVEBMGS00vijaydev] [jstartxx.c 841]

[Thr 5788] *** WARNING => INFO: Unknown property [instance.en.host=vijaydev] [jstartxx.c 841]

[Thr 5788] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]

[Thr 5788] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

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

JStartupReadInstanceProperties: read instance properties [D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties]

-> ms host : vijaydev

-> ms port : 3901

-> OS libs : D:\usr\sap\DEV\DVEBMGS00\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

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

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

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

Instance properties

-> ms host : vijaydev

-> ms port : 3901

-> os libs : D:\usr\sap\DEV\DVEBMGS00\j2ee\os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

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

-> [01] bootstrap_ID7053300 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

-> [02] bootstrap_ID7053350 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

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

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

Worker nodes

-> [00] ID7053300 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

-> [01] ID7053350 : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\instance.properties

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

[Thr 5788] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 5788] JLaunchRequestQueueInit: create pipe listener thread

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

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

[Thr 5788] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 5788] CPIC (version=700.2006.09.13)

[Thr 5788] [Node: server0] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_17

[Thr 5788] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\DEV\DVEBMGS00\exe\jvmx.jar

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

JStartupIReadSection: read node properties [ID7053350]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : C:\j2sdk1.4.2_17

-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-> java vm version : 1.4.2_17-b06

-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : x86

-> heap size : 1024M

-> init heap size : 1024M

-> root path : D:\usr\sap\DEV\DVEBMGS00\j2ee\cluster\server0

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

-> OS libs path : D:\usr\sap\DEV\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 : D:\usr\sap\DEV\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\DEV\DVEBMGS00\exe\jvmx.jar

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

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 50021

-> shutdown timeout : 120000

Former Member
0 Kudos

Hi Hari Krishna,

When I go through the Trace file it is clearelly stating to UME.

Kindly follw the below steps like you cross check whether these configurations has been done (or) not.

1) If you change the backend Client to a new Client make sure you check whether

SAPJSF

J2EE_ADMIN

J2EE_GUST

Users exists in the new client (or) not. if not create them as the users exists you check the roles for the user SAPJSF and the roles must be SAP_BC_JSF_COMMUNICATION and SAP_BC_JSF_COMMUNICATION_RO roles exists with the profiles generated or not.

2) Go to the Visual Admin tool and chk the SLD service (or) Secure provider service whether which user is existing here as by default it is SAPJSF like we have to maintain the user credentials same like here you change the user to J2EE_ADMIN and maintain the password for User and Client HTML and synch as you have to get the message here is successfull.

3) If you change the UME settings in SYSTEMINFO you need to change also in Config tool in "Secure" parameter/ UME Persistance value here it must be same whether it is ABAP UME (OR) JAVA UME.

4) You configure the JAVA System in the new Client i.e. 800 that you register in ABAP System.

5) Go to Config tool and synch the J2EE_ADMIN Password and restart the Instance.

With Regards,

Prashanth