- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- J2EE engine not starting
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
J2EE engine not starting
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 02-11-2009 2:47 PM
Hi All,
I was deploying Java patches using SDM. While deploying the SAPJEE patch I encountered this problem,wherein the patch got deployed but the J2EE engine failed to come up.
The server0 is showing status stopped in mmc.
I have pasted the content of std_server0.out below.
com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] 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 : 9300
system name : DBW
system nr. : 01
started at : Wed Feb 11 15:19:32 2009
[Thr 12920] 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
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 313 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 15 ms.
Loading: ClusterManager ... 125 ms.
Loading: LockingManager ... 47 ms.
Loading: ConfigurationManager ... 1547 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 110 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service memory started. (32 ms).
Service cross started. (47 ms).
Service file started. (63 ms).
Service runtimeinfo started. (16 ms).
Service cafeucc~api started. (16 ms).
Service timeout started. (62 ms).
Service trex.service started. (78 ms).
Service userstore started. (15 ms).
Service jmx_notification started. (31 ms).
Service p4 started. (94 ms).
Service classpath_resolver started. (16 ms).
Service log_configurator started. (2843 ms).
Service locking started. (0 ms).
Service http started. (141 ms).
Service naming started. (203 ms).
Service failover started. (32 ms).
service webservices ================= ERROR =================
Service appclient started. (78 ms).
Service javamail started. (109 ms).
Service ts started. (94 ms).
Service licensing started. (15 ms).
Service jmsconnector started. (156 ms).
Service cafeugpmailcf started. (94 ms).
Service connector started. (156 ms).
Service iiop started. (110 ms).
Service deploy started. (5734 ms).
Service com.sap.portal.runtime.config.kmreadonly started. (16 ms).
Service MigrationService started. (15 ms).
Service configuration started. (31 ms).
Service bimmrdeployer started. (16 ms).
Service dbpool started. (1468 ms).
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:134)
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)
java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:134)
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)
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Feb 11, 2009 3:19:45 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.
As you can see from the above log the service com.sap.security.core.ume.service failed.
Please help me resolve this issue. I have tried restarting the instance but no luck the error persists.
If you need any other logs do let me know.
Thanks
Mitesh
- SAP Managed Tags:
- NW AS Java Administrator (NWA)
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Mahesh,
Please find the dev_server0 log below.
[Thr 12920] Wed Feb 11 15:19:32 2009
[Thr 12920] *** WARNING => INFO: Unknown property [instance.box.number=DBWDVEBMGS01sirhdbw] [jstartxx.c 841]
[Thr 12920] *** WARNING => INFO: Unknown property [instance.en.host=sirhdbw] [jstartxx.c 841]
[Thr 12920] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c 841]
[Thr 12920] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c 841]
**********************************************************************
JStartupReadInstanceProperties: read instance properties [G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host : sirhdbw
-> ms port : 3900
-> OS libs : G:\usr\sap\DBW\DVEBMGS01\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host : sirhdbw
-> ms port : 3900
-> os libs : G:\usr\sap\DBW\DVEBMGS01\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
-> [00] bootstrap : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID15900300 : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID15900350 : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************
**********************************************************************
Worker nodes
-> [00] ID15900300 : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID15900350 : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************
[Thr 12920] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 12920] JLaunchRequestQueueInit: create pipe listener thread
[Thr 5012] JLaunchRequestFunc: Thread 5012 started as listener thread for np messages.
[Thr 13108] WaitSyncSemThread: Thread 13108 started as semaphore monitor thread.
[Thr 12920] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 12920] CPIC (version=700.2006.09.13)
[Thr 12920] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_12-x64
[Thr 12920] JStartupICheckFrameworkPackage: can't find framework package G:\usr\sap\DBW\DVEBMGS01\exe\jvmx.jar
**********************************************************************
JStartupIReadSection: read node properties [ID15900350]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_12-x64
-> java parameters : -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 -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
-> java vm version : 1.4.2_12-b03
-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 1024M
-> init heap size : 1024M
-> root path : G:\usr\sap\DBW\DVEBMGS01\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : G:\usr\sap\DBW\DVEBMGS01\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 : G:\usr\sap\DBW\DVEBMGS01\exe\jstartup.jar;G:\usr\sap\DBW\DVEBMGS01\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50121
-> shutdown timeout : 120000
**********************************************************************
[Thr 12920] JLaunchISetDebugMode: set debug mode [no]
[Thr 5092] JLaunchIStartFunc: Thread 5092 started as Java VM thread.
[Thr 5092] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
Java Parameters: -Xss2m
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djco.jarm=1
-> arg[ 4]: -XX:MaxPermSize=256M
-> arg[ 5]: -XX:PermSize=256M
-> arg[ 6]: -XX:NewSize=171M
-> arg[ 7]: -XX:MaxNewSize=171M
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -verbose:gc
-> arg[ 10]: -Xloggc:GC.log
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -Djava.awt.headless=true
-> arg[ 14]: -Dsun.io.useCanonCaches=false
-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 16]: -XX:SurvivorRatio=2
-> arg[ 17]: -XX:TargetSurvivorRatio=90
-> arg[ 18]: -Djava.security.policy=./java.policy
-> arg[ 19]: -Djava.security.egd=file:/dev/urandom
-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 23]: -Dsys.global.dir=G:\usr\sap\DBW\SYS\global
-> arg[ 24]: -Dapplication.home=G:\usr\sap\DBW\DVEBMGS01\exe
-> arg[ 25]: -Djava.class.path=G:\usr\sap\DBW\DVEBMGS01\exe\jstartup.jar;G:\usr\sap\DBW\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 26]: -Djava.library.path=C:\j2sdk1.4.2_12-x64\jre\bin\server;C:\j2sdk1.4.2_12-x64\jre\bin;C:\j2sdk1.4.2_12-x64\bin;G:\usr\sap\DBW\DVEBMGS01\j2ee\os_libs;C:\Program Files\HP\NCU;C:\Program Files\VERITAS\NetBackup\bin;G:\oracle\VBW\102\bin;G:\oracle\DBW\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\usr\OV\bin;C:\usr\OV\bin\OpC;G:\usr\sap\DBW\SYS\exe\uc\NTAMD64
-> arg[ 27]: -Dmemory.manager=1024M
-> arg[ 28]: -Xmx1024M
-> arg[ 29]: -Xms1024M
-> arg[ 30]: -DLoadBalanceRestricted=no
-> arg[ 31]: -Djstartup.mode=JCONTROL
-> arg[ 32]: -Djstartup.ownProcessId=7528
-> arg[ 33]: -Djstartup.ownHardwareId=J0146219186
-> arg[ 34]: -Djstartup.whoami=server
-> arg[ 35]: -Djstartup.debuggable=no
-> arg[ 36]: -Xss2m
-> arg[ 37]: -DSAPINFO=DBW_01_server
-> arg[ 38]: -DSAPSTART=1
-> arg[ 39]: -DCONNECT_PORT=4023
-> arg[ 40]: -DSAPSYSTEM=01
-> arg[ 41]: -DSAPSYSTEMNAME=DBW
-> arg[ 42]: -DSAPMYNAME=sirhdbw_DBW_01
-> arg[ 43]: -DSAPPROFILE=G:\usr\sap\DBW\SYS\profile\DBW_DVEBMGS01_sirhdbw
-> arg[ 44]: -DFRFC_FALLBACK=ON
-> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 46]: -DSAPSTARTUP=1
-> arg[ 47]: -DSAPSYSTEM=01
-> arg[ 48]: -DSAPSYSTEMNAME=DBW
-> arg[ 49]: -DSAPMYNAME=sirhdbw_DBW_01
-> arg[ 50]: -DSAPDBHOST=sirhdbw
-> arg[ 51]: -Dj2ee.dbhost=sirhdbw
**********************************************************************
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 5092] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [server0]
**********************************************************************
[Thr 5996] Wed Feb 11 15:19:33 2009
[Thr 5996] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 5996] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 5996] JLaunchISetClusterId: set cluster id 15900350
[Thr 5996] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 5996] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 13036] Wed Feb 11 15:19:45 2009
[Thr 13036] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 13036] **********************************************************************
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 13036] JLaunchCloseProgram: good bye (exitcode = -11113)
The thread you suggested does not match my scenario. I have not done any changes to UME. After deploying SAPJEE17 patch the J2EE instance did not come up. Prior to that it was running fine.
Regards
Mitesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hai,
Check the below link.....may help!!
Please check SAP Note: 940893, Point no: 4.
Regards,
Yoganand.V
Edited by: Yoganand Vedagiri on Feb 11, 2009 8:25 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi KVR,
The problem is resolved.As per the link you posted I deployed the SAPJEECOR and SAPJTECHS component and now my JAVA engine is running fine. But it is strange that while deploying SAPJEE SDM did not show any dependency for the component.I have rewarded points for your helpful answer.
So I would like to know why SDM did not show any dependency while deploying SAPJEE component.
Thank you all for your prompt replies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Check this link
/message/1520135#1520135 [original link is broken]
and also can you post dev_server0 file
Hope this will help..
Mahesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Is there a enough heap memory?
Thanks,
Manoj Chintawar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP Datasphere's updated Pricing & Packaging: Lower Costs & More Flexibility in Technology Blogs by Members
- Govern SAP APIs living in various API Management gateways in a single place with Azure API Center in Technology Blogs by Members
- Top Picks: Innovations Highlights from SAP Business Technology Platform (Q1/2024) in Technology Blogs by SAP
- Trustable AI thanks to - SAP AI Core & SAP HANA Cloud & SAP S/4HANA & Enterprise Blockchain 🚀 in Technology Blogs by Members
- Understanding the Data Review steps in Onboarding and the impact on Employee Central in Technology Blogs by SAP
| User | Count |
|---|---|
| 84 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.