Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 445657

Summary: Failed to download image for entry 'Groovy-Eclipse for Juno 2.7.1' (321859) f... (err_grp: a9fe30d6)
Product: [Technology] MPC Reporter: Marcel Bruch <marcel.bruch>
Component: wizardAssignee: Carsten Reckord <reckord>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: cedric.brun, error-reports-inbox, marcel.bruch, mpc.wizard-inbox, reckord
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=446005
Whiteboard:

Description Marcel Bruch CLA 2014-10-01 09:02:09 EDT
Hello committers,

we received a new error report for Eclipse 4.4.1.M20140925-0400.


General Information:
    anonymous-id:         f374816c-5ee0-438c-8c24-61afc9b93747
    eclipse-build-id:     4.4.1.M20140925-0400
    eclipse-product:      org.eclipse.epp.package.jee.product
    operating system:     Windows7 6.1.0 (x86_64) - win32
    java-runtime-version: 1.8.0_05-b13

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.epp.mpc.core_1.3.1.v20140820-1706
    2. org.eclipse.epp.mpc.ui_1.3.1.v20140908-1651
    3. org.eclipse.equinox.p2.transport.ecf_1.1.0.v20140408-1354


Error Status:
    code:                   4
    message:                Failed to download image for entry 'Groovy-Eclipse for Juno 2.7.1' (321859) from http://marketplace.eclipse.org/sites/default/files/styles/medium/public/groovy-logo-medium.png?itok=xoVb7Upt
    fingerprint:            a9fe30d6
    exception class:        org.eclipse.core.runtime.CoreException
    exception message:      Unable to read repository at http://marketplace.eclipse.org/sites/default/files/styles/medium/public/groovy-logo-medium.png?itok=xoVb7Upt.
    number of children:     0

Topmost Stacktrace:
 org.eclipse.core.runtime.CoreException: Unable to read repository at http://marketplace.eclipse.org/sites/default/files/styles/medium/public/groovy-logo-medium.png?itok=xoVb7Upt.
    at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:180)
    at sun.reflect.GeneratedMethodAccessor37.invoke(null:-1)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35)
    at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:107)
    at org.eclipse.epp.internal.mpc.ui.catalog.AbstractResourceRunnable.run(AbstractResourceRunnable.java:70)
    at org.eclipse.epp.internal.mpc.ui.catalog.AbstractResourceRunnable.call(AbstractResourceRunnable.java:57)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
 caused by: org.eclipse.core.runtime.CoreException: 
    at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.wrap(RepositoryStatusHelper.java:177)
    at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:467)
    at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:398)
    at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:240)
    at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172)
    at sun.reflect.GeneratedMethodAccessor37.invoke(null:-1)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35)
    at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:107)
    at org.eclipse.epp.internal.mpc.ui.catalog.AbstractResourceRunnable.run(AbstractResourceRunnable.java:70)
    at org.eclipse.epp.internal.mpc.ui.catalog.AbstractResourceRunnable.call(AbstractResourceRunnable.java:57)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    

Messages, stacktraces, and nested status objects may be shortened. Please visit 
http://dev.eclipse.org/recommenders/reports/542bfb52e4b0fdd807ac4a1b
for the complete error log.

The list of all reported error reports belonging to this error group can be
fetched from http://dev.eclipse.org/recommenders/states/542bfb52e4b0fdd807ac4a1c/reports

The Error Log Reporter presents the current processing state of this error to 
new reporters. This state can be updated by modifying the values of this bug.
To update the error log database call the link below after each change made to
this bug report: http://dev.eclipse.org/recommenders/states/542bfb52e4b0fdd807ac4a1c/sync


Thank you for caring.
Your friendly error reports bot.


--
* Note: The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.
Comment 1 Marcel Bruch CLA 2014-10-06 01:05:33 EDT
*** Bug 446006 has been marked as a duplicate of this bug. ***
Comment 2 Marcel Bruch CLA 2014-10-06 03:52:21 EDT
Hi Carsten, I get this error from three different users on three different products. Is this worth looking at?
Comment 3 Carsten Reckord CLA 2014-10-07 05:43:07 EDT
This indicates a failed download of an entry's icon. There are a number of reasons why this could happen - from a broken icon url to network issues. Unfortunately, the stack trace doesn't contain the root cause and the link to the full log is broken. It works for me right now.

This is non-critical, since the entry gets a fallback image instead, and I thought I had already downgraded it to a warning in the past. I'll look into that.
Comment 4 Marcel Bruch CLA 2014-10-07 06:27:30 EDT
Please let me know if I could improve the logging side somehow. Maybe you can also improve the log message to provide more information next time.



Just to state it once somewhere:

Reports we receive are not severe issues by default and may well be temporary issues.
I just want to support your statement so that other notification receivers don't interpret them as such.

I appreciate your responsiveness and way how you handle these reports!
Comment 5 Carsten Reckord CLA 2014-11-10 08:32:18 EST
*** Bug 447386 has been marked as a duplicate of this bug. ***
Comment 6 Carsten Reckord CLA 2014-11-10 08:35:55 EST
*** Bug 449333 has been marked as a duplicate of this bug. ***
Comment 7 Carsten Reckord CLA 2014-11-10 12:56:59 EST
Changed the log entry to a warning in commit 9ab796d1f28a9a4711dc41bee44c12220118adb5. Seems I forgot about that the last time around...
Comment 8 EPP Error Reports CLA 2014-11-26 08:02:30 EST
To date this log entry was reported 10 times.

Your friendly error reports bot.
Comment 9 EPP Error Reports CLA 2014-12-04 23:50:24 EST
To date this log entry was reported 25 times.

Your friendly error reports bot.