Community
Participate
Working Groups
I've been getting this today both at home and at work. Doesn't seem to make a difference but my last try had build I20100225 and the releng tools from the update site. I'm using the release tool to do the submission for the I-build but whenever I hit the next button to go to the page with the bug list I get the following error: eclipse.buildId=I20100225-1936 java.version=1.6.0_14 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA Command-line arguments: -os win32 -ws win32 -arch x86 Error Mon Mar 01 17:37:37 EST 2010 An internal error has occurred, consult the error log for details. java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source) at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source) at sun.net.www.http.HttpClient.parseHTTP(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source) at org.eclipse.releng.tools.GetBugsOperation.getBugzillaSummaries(GetBugsOperation.java:229) at org.eclipse.releng.tools.GetBugsOperation$1.run(GetBugsOperation.java:91) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
I'm getting this too. In the case of a read time-out, I wonder if we can at least generate the build notes with the bug numbers. At least we could cross reference them ourselves then.
Ian, I think it's the fetch of this info that's timing out...mostly I get none but depending on wind direction I may see a few from projects that got processed before the timeout (but I wonder if a 'flush' might get some more?).
(In reply to comment #2) > Ian, I think it's the fetch of this info that's timing out...mostly I get none > but depending on wind direction I may see a few from projects that got > processed before the timeout (but I wonder if a 'flush' might get some more?). Yep, I saw the same thing last night. I would sometimes get 1 or 2 responses from bugzilla. Since we are hitting bugzilla for something link (bugs.eclipse.org/XXX), if we get a timeout, we could like print something like Bug XXX -- [Bugzilla information not available] Currently we get nothing in the build notes. Incidentally, after I restarted eclipse, it seemed to work fine. So maybe a flush would help.
Ian, thanks for the 'restart' tip ! I'll tryit tonight when I'm doing the build submission...
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
