Hide Forgot
Description of problem: We are seeing intermittent crashes of Eclipse with an SQLite version error. Version-Release number of selected component (if applicable): eclipse-subclipse.x86_64 1.6.5-6.el6 sqlite.x86_64 3.6.20-1.el6 eclipse-svnkit.x86_64 1.3.0-3.el6 How reproducible: The error seems to happen for a while and then goes away. Steps to Reproduce: 1. Use Eclipse for a while with Subclipse and SVNKit plugins installed. Actual results: Eclipse crashes with SQLite version error message. Expected results: Eclipse should run without crashing. Additional info: I found some web pages that seem to reference similar problems. The comment in the second URL indicates that switching from JavaHL to SVNKit fixed the problem. I believe that all of our users have switched to SVNKit and some are still getting this error. https://issuetracker.springsource.com/browse/STS-636 https://bugs.eclipse.org/bugs/show_bug.cgi?id=312424#c23 http://www.eclipse.org/forums/index.php?t=tree&th=159725&
Have you switched to svnkit in Window/Preferences/Team/SVN SVN interface: Client: ? Simply installing eclipse-svnkit won't switch eclipse-subclipse to use it by default.
Can you attach the actual error you're seeing so we can track it better?
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
We have changed the SVN interface field in Preferences. It turns out that the JavaHL option doesn't work with Google Code's SVN server. The SVNKit option does work. The class which uses this is meeting soon. I'll ask them to let me know as soon as someone encounters the error.
Created attachment 492170 [details] screenshot of error message pop-up A student had told me about the problem and I asked her to start Eclipse. She hadn't run it in a while and it took a while to start up. After she started it, she clicked a couple of tabs of open text editors. Then, she went to the Help menu and selected Help Contents. That triggered this error. After restarting Eclipse, we were not able to re-trigger the error. I looked in the .metadata/.log file but didn't find any interesting entries that happened today.
In the past, when this error occurred, I asked users to run "eclipse -clean". This seemed to help the problem for most users. On Monday, the SQLite error was happening repeatedly for the instructor. He said that the "eclipse -clean" command didn't help. I asked him to rename his .eclipse directory so that it would be recreated. He says that this stopped the error from happening.
Does Eclipse automatically update plugins when it starts up? It seems like there are a lot of entries in the Installation History. Also, the .eclipse directory is very large (>100 MB) for our users, even though I have tried to install plugins in the dropins directory.
A user just reported this problem again. I noticed many lines like the following in the .metadata/.log file. I don't know if it is related to the SQLite version error. !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2011-04-21 14:44:47.799 !MESSAGE The installable unit org.eclipse.linuxtools.oprofile.core.linux.x86_64. translated_host_properties is missing the filename property.
We had another incidence of this problem today. I tried running eclipse -clean, eclipse -initialize, and renaming the .eclipse directory. None of these actions seemed to help the problem. What seems to have helped to resolve this problem was to check out the SVN repo into a new workspace. We then had to copy updated versions of the files from the old workspace to the new workspace. When the new workspace is opened in eclipse, the problem no longer occurs. The student noted that they worked all weekend on one computer without this problem occurring. When they worked on a different computer today, the problem occurred.
It should be noted that we have use disk quota system and that users sometimes reach their quotas which can cause file errors. I know that users get this error when they are below their quotas so it is not directly caused by the quota file errors. I don't know if file errors caused by the quota could cause some Eclipse metadata to become corrupted in an uncorrectable way.
Latest Eclipse offering for RHEL6 is now provided in Developer Toolset.