on 11-27-2013 8:33 AM
The problem is pretty understandable.
You only have 8 GB of memory and there is Database, ABAP, Java and SMD running.
For sure the system is undersized.
If possible consider adding more memory to the server.
The only thing I can suggest is to reduce the heap memory for the Java server node from 2 GB to 1GB. For that you need to change the -Xmx and -Xms to value 1024 and restart the Java stack.
This is something not which is not recommended according to the SAP note.
1603093 - SAP JVM 4.1 parameters NetWeaver 2004 and 7.0
There is not need to run Jcmon. You need to select the "AS Java Process table" in the SAP MMC to see the status of the J2EE processes.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check the below note:-
Also, Please share the screenshot of the error now.
Regards,
Himanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sharman,
the link is great but all my settings looking good or according with the recommended and I still don´t know why this is not running.
It was running perfect since the license problems. it was running with a temp license and it expired and I lost connections till i request a new one that gave me problems because of the product choose. so I had to chose a new product that was Standard Java and not the J2EE.
Now i don´t know if that was the problem
Please advise.
Regards,
Nelson Chamba
Hi,
Could you please paste the output of JCMON in your command prompt.
Use the below comand in your system:-
login with sidadm and open cmd:-
jcmon pf=/usr/sap/<SID>/sys/profile/<SAPSID>_<INSTANCE_ID>_<HOST>
useful link for jcmon:
http://help.sap.com/saphelp_nw04/helpdata/en/d3/4d074147c1f06fe10000000a1550b0/content.htm
Regards,
Himanshu
Hi all,
SAP Support team is suggesting this
(1) Please check if OS reboot could resolve your problem.
(2) If not, please shutdown NetWeaver Java (leave ABAP running),
and make sure there's enough physical memory (at very least 3GB).
(3) You can launch configtool and assign 1.5GB max heap size AND xms
for server node and restart AS Java, and see if it could be started.
My question is how do I do the step (2)?
Best regards,
nelson chamba\
(1) Please check if OS reboot could resolve your problem.
You already tried this.
(2) If not, please shutdown NetWeaver Java (leave ABAP running), and make sure there's enough physical memory (at very least 3GB).
Tx SMICM
(3) You can launch configtool and assign 1.5GB max heap size AND xms for server node and restart AS Java, and see if it could be started.
Check my suggestion in the last reply.
Regards
RB
Error occurred during initialization of VM
Could not reserve enough space for object heap
[Thr 6024] JLaunchIAbortJava: abort hook is called
If possible restart the server and then start SAP Java manually.
835704 - Java VM fails to initialize with Startup Framework
http://wiki.scn.sap.com/wiki/display/TechTSG/(JSTTSG)(Kernel)SF-JDK-ObjectHeap
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nelson,
What is the reason for the restart ?
Reason for asking is when we load packages it takes sometime up to an hour for java to start the first time
As requested please upload the logs
Best Regards
Marius
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nelson,
what changes was made on the system because
Error occurred during initialization of VM
Could not reserve enough space for object heap
you seem to be running out of memory,
have a look at this thread : http://scn.sap.com/thread/920222
Best Regards
Marius
Hi Nelson,
Check this sap KBA
1737755 - NetWeaver 04/04s: Dispatcher running but no server connected
regards
kartik
Hello Nelson,
At dev_server0 log:
Error occurred during initialization of VM
Could not reserve enough space for object heap
[Thr 5528] JLaunchIAbortJava: abort hook is called
[Thr 5528] **********************************************************************
[Thr 5528] *** ERROR => The Java VM aborted unexpectedly.
[Thr 5528] *** Please see SAP Note 943602 , section 'Java VM crashes'
[Thr 5528] *** for additional information and trouble shooting.
[Thr 5528] **********************************************************************
[Thr 5528] JLaunchCloseProgram: good bye (exitcode = -2)
Make changes according to note 1658950 - J2EE System fails with "exitcode = -2"
BR,
K.
Hello
Is it possible to restart the server and then start the SAP system ?
I wouldn't suggest changing any of he parameters now as the heap parameters are already set with the standard values.
What is the memory available on the machine ? You need to make sure that there is sufficient memory available on the server for the ABAP, JAVA and the database.
Regards
RB
Hi Nelson,
Please paste the logs of jvm: dev_disp and dev_jcontrol etc in /work folder.
also logs at location usr\sap\SID\JC<>\j2ee\cluster\server\\log.
from the screenshot i suppose you should wait for sometime as i can see some processes are running and then check the url.
Regards,
Himanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nelson,
Upload logs such as bootstrap, dev_disp, sever.out jcontrol to investigate.
BR,
K.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
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.