Community
Participate
Working Groups
eclipse SDK 3.5M2. Try install IU (installable unit) using p2 director application (org.eclipse.equinox.p2.director.app.application) from command line with -consolelog: mupliple exceptions + extremely bad performance (but finally IU installed successfully). Consolelog attached (java -jar /home/builder/kafka/build/eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v20080825-1800.jar -application org.eclipse.equinox.p2.director.app.application -metadataRepository http://download.eclipse.org/modeling/mdt/updates/interim/ -artifactRepository http://download.eclipse.org/modeling/mdt/updates/interim/ -installIU org.eclipse.uml2.sdk.feature.group -version 2.2.100.v200808270930 -nosplash -consolelog)
Created attachment 113428 [details] consolelog
For the proxy NPEs, you can look at bug 246065. I don't know if that's the cause behind the "bad performance" or not though.
Not just "bad performance" but p2 director application update command in 3.5M2 simply hangs. And this is milestone??? severity: normal -> critical. It seems patch attached to https://bugs.eclipse.org/bugs/show_bug.cgi?id=246065 fixes the problem.
Note the bad performance is caused by: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg02781.html
(In reply to comment #4) > Note the bad performance is caused by: > http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg02781.html In scenario above, all IUs installed from LOCAL update site. Are there any reasons to traverse remote URLs supplied in feature manifests or any other remote URLs? Maybe it's good idea to supply some update manager option (don't access remote hosts on install from local or archived update site, or don't access remote host again if first attempt failed)?
*** This bug has been marked as a duplicate of bug 235923 ***