Recently we upgraded all our WebLogic domains to use JRockit from Sun JDK 1.4. After we restarted our servers we started seeing a JRockit dump in few of our servers. After some research and advice from Oracle Support team we were able to start our servers without the crash only if we add the JVM flag “-Xverify:all”. In case you run into this issue you can get over this by adding this flag. The crash dump looks as shown below:
===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 00:02:32 on Wed Oct 1 09:25:47 2008
Additional information is available in:
/opt/satya/fooDomain/jrockit.30205.dump
/opt/satya/fooDomain/core or core.30205
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error Message: Illegal memory access. [54]
Signal info : si_signo=11, si_code=2 si_addr=(nil)
Version : BEA JRockit(R) R27.2.0-131-78843-1.4.2_13-20070320-1511-linux-ia32
GC Mode : Garbage collection optimized for throughput
GC Strategy : Generational Parallel Mark & Sweep
: Current OC phase is: not running. YC is not running.
: GC strategy for GC 7 was genparpar
: GC strategy for GC 8 was genparpar
: GC strategy for GC 9 was singleparpar
: GC strategy for GC 10 was genparpar
: GC strategy for GC 11 was singleparpar
Powered by FireStats
Hi Satya
Any ideas why this error occurs. Pointer to right resources would be appreciated.
BTW, you have an excellent technology blog which has useful practical tips and tricks. And it is no wonder that all these good stuff is coming from the great mind. Your experience, hands of knowledge, industry presence and profile is pretty impressive.
Keep it up,
Thanks,
Phoenix2Life
Thank You for your comments.
We have been working with Oracle Support team and their explanation is that JRockit has some issues with axis code and it crashes in apache axis code whenever a soap request is submitted to a webservice on weblogic. The reason for the crash is that there are two versions of javax.xml.soap.SOAPPart, and the wrong one is loaded ahead of the right one. If you would like to follow up you can refer to CR264864.
Good luck.
Hi Satya,
We are facing the same problem of JVM crashing with Illegal Memory Access. We are running on BEA 8.1 SP4 with jrockit-R27.6.0-jre1.4.2_17. We do use Apache Axis version 1.3 2244 client to invoke a webservice.
Your help is greatly appreciated.
Thank you
Vinay
http://makeonlinemoneyinf.blogspot.com/
You can fine some relvent information about” how to make money online” here also, there you will find some important links of wensites which are doing great job for you in your interest.
http://makeonlinemoneyinf.blogspot.com/