[John]

I have recently upgraded to MyEclipse 7.1.1 – I believe this is the latest version. Since the upgrade I get the following error when attempting to start MyEclipse:

‘An error has occured. See the logfile’.

Running Ubuntu 8.10 OS. (32bit).

With the error I cannot start MyEclipse at all, and naturally cannot do any development at all.

Extract from the log file:

!SESSION 2009-03-11 23:32:21.761 ———————————————–
eclipse.buildId=unknown
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_ZA
Framework arguments: –clean
Command-line arguments: -os linux -ws gtk -arch x86 -clean –clean

!ENTRY org.eclipse.equinox.app 0 0 2009-03-11 23:32:31.106
!MESSAGE Product com.genuitec.myeclipse.product7.ide could not be found.

!ENTRY org.eclipse.equinox.p2.core 4 0 2009-03-11 23:32:32.736
!MESSAGE Provisioning exception
!STACK 1
org.eclipse.equinox.internal.provisional.p2.core.ProvisionException: Unable to read repository at file:/home/moodiejo/Genuitec/Profiles/MyEclipse 7.0/configuration/org.eclipse.osgi/bundles/441/data/listener_1925729951/.
at org.eclipse.equinox.internal.provisional.spi.p2.artifact.repository.SimpleArtifactRepositoryFactory.load(Unknown Source)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(Unknown Source)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(Unknown Source)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(Unknown Source)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.initializeArtifactRepository(Unknown Source)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.RepositoryListener.<init>(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.<init>(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.watchDropins(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1077)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
Caused by: java.io.FileNotFoundException: /home/moodiejo/Genuitec/Profiles/MyEclipse 7.0/configuration/org.eclipse.osgi/bundles/441/data/listener_1925729951/artifacts.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
… 22 more
!SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 1000 2009-03-11 23:32:32.737
!MESSAGE Unable to read repository at file:/home/moodiejo/Genuitec/Profiles/MyEclipse 7.0/configuration/org.eclipse.osgi/bundles/441/data/listener_1925729951/.
Type :quit<Enter> to exit Vim

[Scott Anderson]

MOODIEJO,

That’s very strange as yours is the first report of a problem with the upgrade. However, I’m sure we can sort it out quickly. Can you answer a few questions so we can focus our efforts a bit?

1) What MyEclipse version were you upgrading from? MyEclipse 7.0, or MyEclipse 7.1 that we released a few days ago?
2) How did you originally install MyEclipse? For example, did you use the installer for Linux from our download page? Did you install via an update site? Through Pulse? Or some other mechanism?
3) How did you find out about the update? For example, did you see it on the MyEclipse Dashboard that shows up at startup and select install? Or did you follow some other path?
4) How are you trying to launch MyEclipse right now when you see it fail?
5) Did you user permissions in the install location or account information change recently?
6) Are you running as the same user that performed the install? What about the user that performed the upgrade?

With these answers we should be able to quickly determine what’s going on and how to help.

[John]

Hi,

Thanks for the quick response, herewith the answers you need(hopefully)

1) What MyEclipse version were you upgrading from? MyEclipse 7.0, or MyEclipse 7.1 that we released a few days ago?
[John] 7.1 – Upgraded to 7.1 this evening, then after restart I noticed 7.1.1 was available. 7.1 installed and it ran. After the update to 7.1.1 the issues started.
2) How did you originally install MyEclipse? For example, did you use the installer for Linux from our download page? Did you install via an update site? Through Pulse? Or some other mechanism?
[John] I used pulse
3) How did you find out about the update? For example, did you see it on the MyEclipse Dashboard that shows up at startup and select install? Or did you follow some other path?
[John] From the dashboard.
4) How are you trying to launch MyEclipse right now when you see it fail?
[John] – Same way as normal – ‘Applications’–> Programming–>MyEclipse 7.0
5) Did you user permissions in the install location or account information change recently?
[John] Not that I am aware of – I cannot imagine that this could have happened as I have not recently changed anything here.
6) Are you running as the same user that performed the install? What about the user that performed the upgrade?
[John] Yes, only 1 user on my laptop – moodiejo. Use sodu when needed, but generally only use moodiejo

[John]

Point 6 – sodu = sudo

[Scott Anderson]

John,

Can you try launching the Pulse Explorer, right-clicking on your MyEclipse profile and selecting “Reinstall then run…” from the context menu. Does that correct the problem?

If “Reinstall then run…” does not correct the problem, can you try creating a new MyEclipse profile within the Pulse Explorer and installing that in a different location. It will be really quick because nothing really needs to be downloaded. Does this new profile run correctly?

[John]

Nope, Pulse also reports:

An error has occured. Please see the log file /home/moodiejo/Genuitec/Pulse Explorer/workspace//metadata/.log. Attached the log:

!SESSION Thu Mar 12 00:54:40 GMT+02:00 2009 ————————————
!ENTRY org.eclipse.equinox.launcher 4 0 2009-03-12 00:54:40.654
!MESSAGE Invalid splash path entry: platform\:/base/plugins/org.eclipse.platform
!SESSION 2009-03-12 00:54:40.648 ———————————————–
eclipse.buildId=unknown
java.fullversion=GNU libgcj 4.3.2
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_ZA
Command-line arguments: -os linux -ws gtk -arch x86

!ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2009-03-12 00:54:42.064
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: org.eclipse.equinox.simpleconfigurator_1.0.0.200902181700
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:247)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:201)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:644)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:313)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at java.lang.reflect.Method.invoke(libgcj.so.90)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

!ENTRY org.eclipse.osgi 4 0 2009-03-12 00:54:42.941
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.200902051940.jar/ was not resolved.

!ENTRY org.eclipse.osgi 4 0 2009-03-12 00:54:43.859
!MESSAGE Application error
!STACK 1
java.lang.NoClassDefFoundError: com.genuitec.pulse2.common.http.PulseCommunications
at java.lang.Class.initializeClass(libgcj.so.90)
at com.genuitec.pulse2.client.launcher.ui.product.LauncherApplication.start(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

[Scott Anderson]

John,

Here’s the problem:

java.fullversion=GNU libgcj 4.3.2

Pulse can’t run with GNU libgcj. It requires a “real” Java JRE, like Sun’s. Can you update your path so a Sun ‘java’ will be found first? That’s what likely changed recently for some reason. Also, you can point to a JRE just for Pulse by opening the pulse-explorer.ini file and adding an argument that points to your JRE with something like:

-vm /usr/java/j2sdk1.5.0/bin/java

such that it actually points to a java executable as installed on your machine (that’s just an example above).

[John]

Hi,

Thanks for the great support thus far. Pulse is now running. I will attempt the MyEclipse re-install as suggested and let you know the outcome. It might be worthwhile to check the 7.1.1. install – MyEclipse was working earlier this evening. Pulse was also running earlier this week. All seemed to work prior to the upgrade to 7.1.1.

Cheers.

John

[Scott Anderson]

John,

Oh, trust me, we checked on every platform and both 32 and 64 bit just after the release and didn’t find any problems. But if Pulse was running early in the week, it was definitely finding a JRE then. So that’s peculiar that it’s picking up libgcj now instead.

Please let us know what you find out.

[John]

Once again, your support was tremendous. Thanks for this. Re-install running, but this will take a while to complete. Broadband not that broad. Will update you on the outcome.

[rajan.deepu.java]

I have installed MyEclipse on Eclipse Classic using the updates manager, But after I feed in the subscription key which was working for windows the Finish Button is grayed out. I am using JDK 6 on Ubuntu 8.10.

[support-joy]

I have replied to your post here – https://www.genuitec.com/forums/topic/ubuntu-8-10-subscription-key-finish-grayed-out/#post-298109

[Author]

Posts