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.
Continue reading here
A blog on Java Middleware technologies
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.
3 comments:
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
Post a Comment