Community
Participate
Working Groups
I was performing a Update to get the EMF source and documentation features. After finishing the wizard I choose to run in the background. After a while, another progress dialog popped up and blocked me. It said it was verifying something. After a while, I got an error dialog with the message: Unable to complete action for feature "Eclipse Modeling Framework (EMF) Source" due to errors. Unable to retrieve remote reference "http://update.eclipse.org/updates/3.0/features/org.eclipse.emf.sourc e_2.0.1.jar". [Operation timed out: connect:could be due to invalid address] Unable to retrieve remote reference "http://update.eclipse.org/updates/3.0/features/org.eclipse.emf.sourc e_2.0.1.jar". [Operation timed out: connect:could be due to invalid address] This is odd since it is the official Eclipse update site but it is probably an issue with the site and not the update manager.
It appears that the Eclipse Update site just went down so that would be the cause of the error messages. Given that the site is down, I can't verify the first problem during a success case (i.e. I don't know if the progress dialog comes up in every case or just when there is a failure). If it only happens during a failure, it is less severe.
Instead of opening several bug reports, I'm going to dump all my problems here. You can decide if you want a separate bug report and let me know;-) I tried another update but from a secondary site that EMF provides (i.e. it's on Eclipse.org but not the official site). WHen I tried this, I was prompted to select a mirror which I did. After the install page was populated with the features on the secondary site, I got an error dialog with the following errors: Network connection problems encountered during search. Unable to access "http://netmirror.org/mirror/eclipse.org/eclipse/updates/3.0/". Unable to access site: "http://netmirror.org/mirror/eclipse.org/eclipse/updates/3.0/" [Server returned HTTP response code: "404 Not Found" for URL: http://netmirror.org/mirror/eclipse.org/eclipse/updates/3.0/.] Unable to access site: "http://netmirror.org/mirror/eclipse.org/eclipse/updates/3.0/site.xml" [Server returned HTTP response code: "404 Not Found" for URL: http://netmirror.org/mirror/eclipse.org/eclipse/updates/3.0/site.xml.] Dismissing the dialog allowed me to continue. I'm not sure if the specific error is worth addressing since, it appears to me, that the whole mirror funtionality of the Update wizard needs revisiting. Wouldn't it be better to add the mirrors to the list of availabel update sites and allow the user to select which site to try? P.S. I get the Verify progress dialog on a success case as well. This is bad because if the user happens to be typing in an editor at the same time this progress dialog pops up, they may inadvertantly cancel the update which would be bad.
Thanks Michael, this is all good info. Here are some comments: 1. the verification message is part of feature install. Basically each feature jar is looked at for digital signatures (this is actually a very slow process, as each file in the jar is looked at). 2. I am not sure why the first error message appears *after* the verification message. That seems a bit odd to me. 3. there were problems with the mirror url that Denis fixed 4. yes, the mirroring needs a bit more polishing (I have a bug opened on that), but any feedback you have would be useful. Right now, the main thing that needs to be done is adding a checkbox so the user is not prompted for the same mirrors again, and second, during updates, to only display the mirror selection dialog once. 5. back to the verify dialog: is there a nice way to tell the use that something is pending? (in this case an install operation)
What do you mean by "pending"? My complaint was that I chose to run in the background and half way through I get a progress dialog. Can the verification run in the background or does it need to be a foreground operation?
Yes, verifican can run in the background, but because of the way update code is structured (verification is called by Feature.install()), right now verification is not done in the background. Some refactoring is needed to move all verification code in the background, and leave only the final install step to be done modally.
Michael, did you try this in 3.2? Verification shouldn't produce this kind of problems anymore. We do not contact server during verification anymore.
Seems to work OK in 3.2.
thanks michael. *** This bug has been marked as a duplicate of 144876 ***
