What would cause Error Event ID 7024 for Websphere?
Accepted answer
As far as I know RRDI 1.0 requires WAS 32 bit which does not allow to allocate so much memory. Here are the steps to correct this option:
1. Open your WAS profile console
2. click Under Server Infrastructure, click Java and Process Management > Process definition.
4. Under Additional Properties, click Java Virtual Machine.
5. Add the value 512 to Initial Heap.
6. Add the value 1500 to Maximum Heap Size.
7. Restart your WAS profile
Let us know if it helps for you.
Best reagards,
Krzysztof Kazmierczyk
Comments
Hi Krzysztof, I thought the 32bit constraint was only for the DB client. Please provide a link to the article where it states this 32bit constraint is applicable to the application server.
Hi Abraham,
Sure. Look at this: http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.rational.rcpr.help.doc/topics/r_system_software_repserver.html
Changing the heap size solved the problem. Thanks everyone for your help!
4 other answers
Since the console is not running I think you need to change the Maximum Heap Size editing the server.xml of the RRDI profile in WAS.
Best Regards
Francesco
Comments
Example:
In file
C:\IBM\WAS80\AppServer\profiles\RationalReporting\config\cells\WIN-8COGOPO9D2YNode01Cell\nodes\RationalReportingNode01\servers\RationalReportingServer\server.xml
section
<jvmEntries xmi:id="JavaVirtualMachine_1183122130078" verboseModeClass="false" verboseModeGarbageCollection="false" verboseModeJNI="false" maximumHeapSize="1024" runHProf="false" hprofArguments="" debugMode="false" debugArgs="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=7777" genericJvmArguments="">
Thanks Francesco, I was going to ask how to change the heap size since the server is offline.
http://technet.microsoft.com/en-us/library/cc756369(v=ws.10).aspx
If something catostrophic did occur with the service, then WebSphere processes may still be lingering around. I would do the following:
1. FOllow the steps in the above article to determine what may have happenned
2. On the Windows task manager, confirm that there are no running java processes
3. If there are java processes for WebSphere still running, manually stop them and attempt to then restart WebSphere
4. Check the WebSphere logs to see if it has any information on what could have occurred
Comments
When we would restart Webshpere we made sure that there were no running Java processes. However, the system would crash within 10 minutes. As for an error code, we are seeing 1.
Hi Jim, based on the error message, "JVMJ9GC028E Option too large: '-Xmx6144m' <o:p> </o:p>" IF WIndows is not allocating enough memory to WebSphere, this behavior can be expected.
VMJ9GC028E Option too large: '-Xmx6144m'
JVMJ9VM015W Initialization error for library j9gc24(2): Failed to initialize; unable to parse command line
Could not create the Java virtual machine.
JVMJ9GC028E Option too large: '-Xmx6144m'
And investigating it right now.
Comments
Francesco Chiossi
Aug 09 '13, 9:01 a.m.Hello James,
could you include more details on the error message from the WAS log?
Best Regards
Francesco