Community
Participate
Working Groups
Build Identifier: 20110916-0149 In the folder .metadata\.plugins\org.eclipse.epp.usagedata.recording I have a whole ton of files named something like: upload*.csv dating back a couple of years. The usage collector should rather create a temporary file using the normal File.createTempFile mechanisms, so that these files get deleted periodically. Reproducible: Always
These are not temporary files. At least not in the File.createTempFile sense. Theoretically, the UDC collects data over several days and then uploads it all in one go. When the upload is successful, the files are deleted. If the files are sticking around, then there's a good chance that there's something bad happening when the upload is attempted. Are there any UDC-related messages in the log ([workspace]/.metadata/.log) that might shed some light on why the files are not being removed? I'd be interested specifically in messages indicating that the upload has failed. Are there any messages at all that indicate that the upload was successful? FWIW, work on the UDC has been discontinued. The client portion has been removed from the Juno builds. The server portion has been "turned off": any contact with the server should result in a 200 return code which tells the UDC to delete the cached data. The easy work around here is to delete the files and turn off the UDC. The most complete way to turn off the UDC is to go to the Preferences, "General > Startup and Shutdown", and untick the checkboxes for the two "Usage Data *" plug-ins.
There are lots of messages like this: !ENTRY org.eclipse.epp.usagedata.recording 2 0 2011-12-05 09:53:28.857 !MESSAGE Could not connect to the usage data upload server at http://udc.eclipse.org/upload.php. !STACK 0 java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.<init>(Socket.java:375) at java.net.Socket.<init>(Socket.java:249) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) at org.eclipse.epp.usagedata.internal.recording.uploading.BasicUploader.doUpload(BasicUploader.java:206) at org.eclipse.epp.usagedata.internal.recording.uploading.BasicUploader.upload(BasicUploader.java:129) at org.eclipse.epp.usagedata.internal.recording.uploading.BasicUploader$1.run(BasicUploader.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Probably because it was ignoring the proxy settings. I've turned off the collector as you suggest. There were literally several thousand files in my folder.
That makes sense. With apologies, we never did get around to adding Proxy support. Marking as a duplicate of Bug 336631. *** This bug has been marked as a duplicate of bug 336631 ***
