Bug 500271 - Failed to determine ETAG for remote problems database.
Summary: Failed to determine ETAG for remote problems database.
Status: RESOLVED FIXED
Alias: None
Product: EPP
Classification: Technology
Component: Automated Error Reporting Client (AERI) (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: EPP Error Reports CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2016-08-25 07:12 EDT by Yousha Aleayoub CLA
Modified: 2016-09-14 03:54 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yousha Aleayoub CLA 2016-08-25 07:12:07 EDT 
What steps will reproduce the problem?
1. Just open Eclipse.
2. 
3. 


-- Error Details --
Date: Thu Aug 25 15:27:27 IRDT 2016
Message: Failed to determine ETAG for remote problems database. Stopping update. Version: 1.0.0.v20150617-0732
Severity: Warning
Product: Eclipse 4.5.0.20150621-1200 (org.eclipse.epp.package.java.product)
Plugin: org.eclipse.epp.logging.aeri.ui
Session Data:
eclipse.buildId=4.5.2.M20160212-1500
java.version=1.8.0_102
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product
Comment 1 Jay Arthanareeswaran CLA 2016-08-25 09:42:25 EDT 
I have no idea what the bug description mean nor why this is a JDT core bug. If you could elaborate the problem more, I might be able to move this to the appropriate component.
Comment 2 Stephan Herrmann CLA 2016-08-25 12:32:33 EDT 
I'd say this goes to the Error Reporting project.
Comment 3 Johannes Dorn CLA 2016-09-14 03:54:56 EDT 
Error Reporting is the correct project.

This seems to have been an intermittent problem due to slowness/unavailability of download.eclipse.org. 

I can update the database just fine using Mars.2

Since then, the code for updating the problem database has changed significantly, thus, further problems would yield quite different stacktraces.

Marking this as resolved.