[THEN]

Hello there,

I installed MyEclipse V3.8 RC2 yesterday. As I started Eclipse today, I got an error message from the automatical update search.

OS: WIN XP
Eclipse: Version: 3.0.0 Build id: 200406251208
MyEclipse: Version: 3.7.200 Build id: 200407091200-3.8-Beta2
JDK: j2sdk1.4.2_04

I freshly installed upper eclipse version with MyEclipse 3.8-Beta1 and
upgraded to upper version (with method: deinstalling, restarting,
installing again)

I can reproduce this error by opening the product configuration page, selecting ‘MyEclipse Enterprise Workbench’ and click onto ‘scan for
updates’.

Here is the part of the logfile containing the error message:
!SESSION Jul 16, 2004 13:15:47.103 ———————————————
eclipse.buildId=I200406251208
java.version=1.4.2_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.update.core 4 42 Jul 16, 2004 13:15:47.103
!MESSAGE Network connection problems encountered during search.
!SUBENTRY 1 org.eclipse.update.core 4 42 Jul 16, 2004 13:15:47.103
!MESSAGE Unable to access “http://www.myeclipseide.com/products/eworkbench/updates-3.0/”.
!SUBENTRY 2 org.eclipse.update.core 4 42 Jul 16, 2004 13:15:47.103
!MESSAGE Unable to access site: “http://www.myeclipseide.com/products/eworkbench/updates-3.0/” [http://www.myeclipseide.com/products/eworkbench/updates-3.0/]
!STACK 0
java.io.FileNotFoundException: http://www.myeclipseide.com/products/eworkbench/updates-3.0/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:789)
at org.eclipse.update.internal.core.ConnectionThreadManager$StreamRunnable.run(ConnectionThreadManager.java:75)
at java.lang.Thread.run(Thread.java:534)
!SUBENTRY 2 org.eclipse.update.core 4 42 Jul 16, 2004 13:15:47.103
!MESSAGE Unable to access site: “http://www.myeclipseide.com/products/eworkbench/updates-3.0/site.xml” [http://www.myeclipseide.com/products/eworkbench/updates-3.0/site.xml]
!STACK 0
java.io.FileNotFoundException: http://www.myeclipseide.com/products/eworkbench/updates-3.0/site.xml
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:789)
at org.eclipse.update.internal.core.ConnectionThreadManager$StreamRunnable.run(ConnectionThreadManager.java:75)
at java.lang.Thread.run(Thread.java:534)

!ENTRY org.eclipse.update.configurator Jul 16, 2004 14:15:48.97
!MESSAGE Can’t find bundle for base name feature, locale en_US

I hope I chose the right forum for this issue!

Thomas

[Scott Anderson]

Thomas,

Thanks for alerting us to this. We turned off the update site yesterday because of some upgrading questions with GEF that are caused by usage of the version 3.0.0 by the Eclipse team for all the milestone builds as well as the production builds. Since the platform couldn’t differentiate the new final version from the old ones, the latest GEF was not being installed which caused issues with upgraders. More information is available here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-2915.html

So, we’ve now put enough of the update site back in place to keep this exception from being thrown in the log, but you’ll still need to download one of the double-click or manual installers and use them to upgrade to the latest version. Hope that clears things up.

[THEN]

Eclipse is starting again without error messages. Thank you for the fast reply!

Thomas

@support-scott wrote:

Thomas,

Thanks for alerting us to this. We turned off the update site yesterday because of some upgrading questions with GEF that are caused by usage of the version 3.0.0 by the Eclipse team for all the milestone builds as well as the production builds. Since the platform couldn’t differentiate the new final version from the old ones, the latest GEF was not being installed which caused issues with upgraders. More information is available here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-2915.html

So, we’ve now put enough of the update site back in place to keep this exception from being thrown in the log, but you’ll still need to download one of the double-click or manual installers and use them to upgrade to the latest version. Hope that clears things up.

[Scott Anderson]

No problem. Thanks again for letting us know about it.

[Author]

Posts