Comments on: Eclipse all messed up

by: miki

Thu, 21 Jun 2007 18:06:59 +0100

Hi,
I’m using ubuntu 7.04 and I had the same problem. I reinstalled java (1.5 in my case) and it works now.
That is, go to synoptic and select all java packages you already had and select reinstall.
I hope this will help somebody.

by: Alex

Fri, 18 May 2007 21:51:37 +0100

I have latest ubuntu(fiesty main) and i also have such error. Eclipse starts with it, but then when i try to create j2ee project it crashes with error in jvm.
The most ugly thing is that there is no exception in log, simply this:
!SESSION 2007-05-18 22:37:20.748 ———————————————–
eclipse.buildId=unknown
java.version=1.4.2_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86

!ENTRY org.eclipse.osgi 2 1 2007-05-18 22:37:21.975
!MESSAGE NLS missing message: initializer_error in: org.eclipse.core.internal.runtime.messages

!ENTRY org.eclipse.osgi 2 1 2007-05-18 22:37:21.975
!MESSAGE NLS missing message: fileInitializer_fileNotFound in: org.eclipse.core.internal.runtime.messages

!ENTRY org.eclipse.osgi 2 1 2007-05-18 22:37:21.976
!MESSAGE NLS missing message: fileInitializer_IOError in: org.eclipse.core.internal.runtime.messages

!ENTRY org.eclipse.osgi 2 1 2007-05-18 22:37:21.976
!MESSAGE NLS missing message: fileInitializer_missingFileName in: org.eclipse.core.internal.runtime.messages

I’ve checked fstab:
#
proc /proc proc defaults 0 0
# /dev/sda3
UUID=9ae2d28e-4e20-4c21-85c7-97058bb93e89 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda1
UUID=38F0A171F0A135D2 /media/sda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda2
UUID=6A04A39E04A36C2F /media/sda2 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda4
UUID=a94ed6c9-e1c1-4b0c-bd90-a9636a9414a2 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0

Does jvm have its own log? Because when it crashes nothing is written to log, error messages can be seen only on startup, when it crashes nothing!!!
Better to solve java exceptions, really…..

by: Tim

Thu, 22 Feb 2007 21:17:22 +0000

Now we have two solutions.

I’d tried purging and reinstalling before I found my problem, but it was still stuck. I think that of all the error messages I’ve ever seen, java applications have the worst.

In my case the problem was more general, and some of the other apps had better error messages.

by: Andi

Wed, 21 Feb 2007 12:27:08 +0000

Thanks.
I managed to solve it too, but my problem was something else, I thnink (but I don’t know what). I reinstalled Eclipse, and for the 4th time I selected “Remove completely” not only “Remove” as the first 3 times, then install again.

by: Tim

Tue, 20 Feb 2007 20:27:33 +0000

Yeah. I have it listed at a later post. It was a mmap permission thing. I screwed up, and fixed it. Since then eclipse mostly has been behaving very well.

by: Andi

Tue, 20 Feb 2007 19:17:24 +0000

Hi,
I have the same problem.
Have you found a solution?

Andi