on 11-30-2007 10:31 PM
OS : Win 2k3 Std edition Uk SP 1
DB : Msft SQL Server 2005 (9.0.2047)
Total Physical Memory 3.583,47 MB
ECC 6.0
<b>Hi,
J2EE doesn't start after changement of J2EE Java parameters according SAP Notes : 723909</b>
-
From dev_bootstrap
[Thr 1944] JLaunchIExitJava: exit hook is called (rc = 2)
[Thr 1944] **********************************************************************
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 1944] JLaunchCloseProgram: good bye (exitcode = 2)
-
From jvm_bootstrap
java.lang.ClassNotFoundException: com.sap.engine.bootstrap.Bootstrap
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
-
From std_bootstrap
-
stdout/stderr redirect
-
node name : bootstrap
pid : 4324
system name : ECC
system nr. : 01
started at : Fri Nov 30 22:48:00 2007
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
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
-
<b>Thanks in advance for your feedback
Yves</b>
Hello Yves,
Cross check again the parameters that you have changed.
Also cross check if you have followed every instructions from the OSS note. (including manual corrections)
Check if there are any duplicate parameters that could cause conflict.
Also refer to note:
Note 940893 - Analysis of errors within the startup of J2EE Engine 6.40
Regards,
Ammey Kesarkar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Just kill all the processes which are consuming more memory on you system and then restart Java this will work. Hopefully you haven't changed any parameters whcih are refering to JVM..
Regards
Vivek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
Hard to analyze with the information presented here. Most likely cause is from my point of view that the jvm cannot allocate its memory in a contiguous chunk. Your physical memory is not really big and dependendt on the size of your DB (and ABAP stack(?)) there may simply not be enough memory left for the J2EE, which requires quite a lot of RAM if configured according to SAP standard (which is recommendable normally). E.g. In a 64bit environment a Netweaver7 Java Stack with a single servernode requires around 3.5GB from the OS if configured according to SAP.
So first thing I'd do is limit the amount of memory MSSQL is allowed to take (e.g. to 1024M or even 512M), restart MSSQL to take that into account and see how much memory is still free on your server. Then you should compare this with the parameters of your J2EE. It will probably not look too great and you will have to do some analysis and testing before you get SAP-Java up and running. Another option could be to reverse your changes, start everything and see how much memory is free on your server to get an idea of how much more you can assign for the Java-Stack without running into problems.
Regards,
Jörg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.