A fatal error has been detected by the Java Runtime Environment. EXCEPTION_ACCESS_VIOLATION

南楼画角 提交于 2019-12-05 01:32:20
Alexei Kaigorodov

This is a bug inside JRE. You can do nothing about this, just send a bug report to the link provided:

http://bugreport.java.com/bugreport/crash.jsp

Try to use 32-bit version instead of 64. Try to use another JRE version (not 6.0_27-b07).

Just dropping by to tell that I got the same error and it went away when I simply rebooted the computer. Try restarting the computer especially when everything was working fine earlier.

I just happened to get this problem too, trying to re-installing the JVM (JDK+JRE) to newer version (7u4 to 7u5) but still getting the same error..

then I change the system classpath to point to the newer JDK 7u5(before was pointing to the directory of the older 7u4 which is not exist by now), and the problem is gone..

I don't know the reason but I got this one works on me.. (oh and yes, changing to 32-bit too)

Rama Satyateja

May be you are using the connection string with integratedSecurity=true make sure that keep the connection string with credentials i.e. DBusername and DBpassword

Note:

  1. This solution will works when the DB is not in localhost.

  2. Make sure that the sqljdbc_auth.dll should be compatable with the hard ware

Solution that worked for me : I was using SQLJDBC Version 4.2 which was causing this error(This was working fine with Windows 7). Now I had upgraded to SQLJDBC Version 6.X and remapped the sqljdbc_auth.dll for 64 bit version to my classpath (there are various ways to map it).

Config info: 1) sqljdbc_6.0.8112.100_enu 2) JDK Version 1.8.0_121 (Also tried with 1.8.0_161) 3) OS-> 64 Bit Windows 10

The error occurred out of Apache code: org.apache.activemq.openwire.OpenWireFormat.unmarshal. It's doing a java.io.DataInputStream.readInt. I'm not familiar with what Apache may be doing at this point, but I suspect it's somehow been passed bad data (lots of opportunities for this in an unmarshal operation), perhaps from the other end of the conversation.

The thread involved is "ActiveMQ Transport: tcp://localhost/127.0.0.1:61616", if that helps at all.

Change the settings of eclipse configuration setting file,which resides in Eclipse folder. please do the following changes: --XMS 40m --XMS 768m

change the second --XMS value by reducing low.

My project also is a maven project having AMQ. In my project there was a parent project with masterVersionNumber and all the sub projects were deriving their version number from it.

Example on the pom of sub project I had <finalName>subProjectName${masterVersionNumber}</finalName> I got the above error.

So my work around was to remove ${masterVersionNumber} and use <finalName>subProjectName4.1.4</finalName> and it worked perfectly fine during the build.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!