WAS 8.0.0.4 does not start after entering generic JVM arguments (CLM 4.0)
Hi
I am trying to configure WAS 8.0.0.4 on Windows 7 (64 bit) Professional edition. While trying to setup WAS and after entering the JVM argments mentioned in http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_s_server_installation_setup_WAS.html I am not able to re-start WAS. So I have to delete the WAS profile and redo the steps with out entering the JVM arguments. It stops and starts properly. Any solutions for the above. Regards V.Niranjan |
Accepted answer
Karl Weinert (2.0k●5●27●36)
| answered Dec 03 '12, 9:43 a.m.
JAZZ DEVELOPER edited Dec 03 '12, 9:46 a.m.
With only 8 gigs of memory I would get rid of the -Xgc:preferredHeapBase=0x100000000setting
That tells the JVM to use memory above the first 4 gigs, so that may be cutting it kind of close. Especially since it requires the memory it uses to be contiguous. You could also try to use a smaller xmx and xms setting * I originally wrote to remove the -Xcompressedrefs setting which is incorrect it should be the -Xgc:preferredHeapBase=0x100000000 setting as corrected above
V Niranjan selected this answer as the correct answer
|
One other answer
Benjamin Silverman (4.1k●6●10)
| answered Dec 02 '12, 11:11 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Usually when WAS fails to start properly after setting a property, it means the property was not set properly, or set to a value too large for the server to handle. The setting can usually be adjusted by modifying the server.xml file rather than deleting the profile and starting over. I suggest checking the systemout or systemerr logs for errors if this happens again so you can determine was is causing the problem.
Typically, this can happen if you set the JVM max heap size to a value larger than 1/2 the physical memory available on the system. For example, if your server only has 4GB of RAM and you've set the max JVM heap to 4GB, WAS will not start under that condition since you need native memory available for the system to function properly. It is also not difficult to make mistakes when setting the generic JVM arguments (ie - entering a ; instead of a :, omitting spaces between the -X properties). I can't say exactly what caused the problem based on the information provided, but I hope it helps, Comments Hi
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.