Skip to Content
0
Former Member
Aug 02, 2007 at 07:45 AM

J2ee is down while applying Java Patches

13 Views

HI,

I have installed java addon to an existing ABAP system.

I have followedBelow steps:

a) Central Services instance(SCS) java addin

b)Database instance for java add in

c)Central Instance for Java addin

I have updated ABAP stsck to SP11, when i am trying to update java stsck to SP11 J2ee is going down.

I am unable to update patches in ABAP.

2) <b>ERROR:</b> <u>"std_server0.out"</u>

Aug 1, 2007 4:48:41 AM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_57] Fatal:

Aug 1, 2007 4:48:41 AM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_57] 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:388)

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'!: Datasource R3_DATASOURCE: Unsupported attribute name "SecurityPolicy". Principal type: UACC, namespace: com.sap.security.core.usermanagement

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

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

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'!: Datasource R3_DATASOURCE: Unsupported attribute name "SecurityPolicy". Principal type: UACC, namespace: com.sap.security.core.usermanagement

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

... 6 more

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

Aug 1, 2007 4:48:41 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_57] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

<u><b>dev_server0</b></u>

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\TEC\SYS\global

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

-> arg[ 26]: -Djava.class.path=D:\usr\sap\TEC\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\TEC\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_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;C:\j2sdk1.4.2_12\bin;D:\usr\sap\TEC\DVEBMGS00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\usr\sap\TEC\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=3408

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

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

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

-> arg[ 37]: -DSAPINFO=TEC_00_server

-> arg[ 38]: -DSAPSTART=1

-> arg[ 39]: -DCONNECT_PORT=1069

-> arg[ 40]: -DSAPSYSTEM=00

-> arg[ 41]: -DSAPSYSTEMNAME=TEC

-> arg[ 42]: -DSAPMYNAME=ecctest_TEC_00

-> arg[ 43]: -DSAPPROFILE=D:\usr\sap\TEC\SYS\profile\TEC_DVEBMGS00_ecctest

-> arg[ 44]: -DFRFC_FALLBACK=ON

-> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 46]: -DSAPSTARTUP=1

-> arg[ 47]: -DSAPSYSTEM=00

-> arg[ 48]: -DSAPSYSTEMNAME=TEC

-> arg[ 49]: -DSAPMYNAME=ecctest_TEC_00

-> arg[ 50]: -DSAPDBHOST=ECCTEST

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

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

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

[Thr 2444] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [server0]

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

[Thr 996] Wed Aug 01 04:48:31 2007

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

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

[Thr 996] JLaunchISetClusterId: set cluster id 5769750

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

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

[Thr 5356] Wed Aug 01 04:48:42 2007

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

[Thr 5356] **********************************************************************

  • 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 5356] JLaunchCloseProgram: good bye (exitcode = -11113)

3) <u><b>DEV_DISP.old</b></u>:

Wed Aug 01 02:16:35 2007

  • ERROR => DpHalt: J2EE (pid 4484) still alive [dpxxdisp.c 10217]

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

DpJ2eeEmergencyShutdown: try to kill SAP J2EE startup framework (pid=4484)

waiting for termination of J2EE server (2nd chance) ...

Wed Aug 01 02:16:36 2007

DpStartStopMsg: send stop message (myname is >ecctest_TEC_00 <)

DpStartStopMsg: stop msg sent

Wed Aug 01 02:16:37 2007

DpHalt: sync with message server o.k.

detach from message server

***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 11976]

MBUF state OFF

MBUF component DOWN

cleanup EM

***LOG Q05=> DpHalt, DPStop ( 5904) [dpxxdisp.c 10333]

!) are there anypre or post-installtion steps to be done for Java addon

2) are there any configuration has to be done for before or after installting java add-on to an existing system

3) do i have to apply for a new licence for java add-on

I have attached the error logs.

Regards,

Mag