I'm experiencing serious issue with the Eclipse 'Install new software' and 'Update' Dialogs.
In fact they seem to do nothing.
With a brand new Eclipse Java EE Juno 4.2 I can't install new software. I try to retrieve the contents of 'Juno - http://download.eclipse.org/releases/juno' but it's stuck all the time. Often is stops doing anything around 31% but sometimes it reaches 38% after 20 minutes but there must be something wrong.
I unticked all the options and also deactivated firewall and antivir and tried to alter the network configurations in eclipse with no effect.
I'm not behind a proxy.
Somebody got a solution on this?
Regards
The Error Log has plenty entries mainly like this:
Unable to read repository at http://download.eclipse.org/releases/juno/201206270900/artifacts.jar.
Unknown Host: http://download.eclipse.org/webtools/patches/drops/R3.4.1/P-3.4.1-20121112163420/repository/content.xml
Connection to http://download.eclipse.org/technology/epp/packages/juno/p2.index failed on Connection reset. Retry attempt 0 started
Connection to http://download.eclipse.org/webtools/patches/drops/R3.4.1/P-3.4.1-20121112163420/repository/p2.index failed on Connection reset. Retry attempt 0 started
Unable to read repository at http://download.eclipse.org/releases/juno/201206270900/content.jar.
Connection to http://download.eclipse.org/releases/juno/201209280900/p2.index failed on Connection reset. Retry attempt 0 started
You could also try with the following option in your STS.ini file, it worked for me:
-Djava.net.preferIPv4Stack=true
Make sure you don't have antivirus (particularly Kaspersky) running. May have to pause your AV program as it could block the process.
Related
I can't update NetBeans, I always get "Unable to connect to the Update Center".
I already checked the windows firewall settings:
I also checked the proxy, I get a green checkmark:
What else can I try?
I am using NetBeans 8.2 (Build 201609300101)
Proxy settings were NOT the problem for me.
I'm running NetBeans 11.0, and see that there are 4 default "Update Centers" configured. Having nothing to do with Proxy settings, I discovered that the "NetBeans Plugin Portal" URL was failing https://netbeans.apache.org/nb/plugins/11.1/catalog.xml.gz, and the last time this site was successfully checked was on 4/20/21.
My solution was to deselect that Update Center, and added the 11.0 archive site instead:
http://plugins.archive.librebeans.org/catalogue/11.0/catalog.xml
Now I can update/install plugins as expected. Maybe this is the solution for you too.
there is a number of similar questions from long ago (e.g. this one), and the suggestions are mainly about misconfigured proxy.
in my case, looking at the IDE log file revealed the following stack trace:
INFO [org.netbeans.modules.autoupdate.services.InstallSupportImpl]: Timeout while opening connection to http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/enterprise/org-netbeans-modules-websvc-metro-lib.nbm
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:205)
at org.netbeans.modules.autoupdate.updateprovider.NetworkAccess$Task$1.run(NetworkAccess.java:111)
Caused: java.io.IOException: Timeout while opening connection to http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/enterprise/org-netbeans-modules-websvc-metro-lib.nbm
at org.netbeans.modules.autoupdate.updateprovider.NetworkAccess$Task$1.run(NetworkAccess.java:131)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
INFO [org.netbeans.modules.autoupdate.services.InstallSupportImpl]: Cannot access http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/enterprise/org-netbeans-modules-websvc-metro-lib.nbm
java.io.IOException: Cannot access http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/enterprise/org-netbeans-modules-websvc-metro-lib.nbm
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.copy(InstallSupportImpl.java:981)
[catch] at org.netbeans.modules.autoupdate.services.InstallSupportImpl.doDownload(InstallSupportImpl.java:733)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.doDownload(InstallSupportImpl.java:661)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.access$600(InstallSupportImpl.java:92)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl$1.call(InstallSupportImpl.java:172)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl$1.call(InstallSupportImpl.java:144)
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)
Because I thought that was nothing wrong with my proxy settings (no proxy is selected, and connection is tested OK), i searched and search, getting even into the NetBeans code, trying in vain to find some hidden Timeout property. Indeed there is a place in the code (AutoupdateSettings.getOpenConnectionTimeout which seems to correspond to plugin.manager.connection.timeout property) which sets a timeout - yet i couldn't make it work (mucking with .properties files in ~/AppData/Roaming/NetBeans/8.2/config/Preferences/org/netbeans/modules/autoupdate)
In the end the only workaround I found was to download the NBM file mentioned in the stack trace manually. It seems that it was either indeed my firewall (an antivirus check?), or the file was just too large in itself and would cause the timeout because of this. Or the overloaded server. Anyway.
Fortunately, it is possible to install the downloaded file through Tools -> Plugins -> Downloaded -> Add Plugins, even though that plugin already is installed. Doing this the update process continued normally (although there was another timeout later - so I repeated the above procedure) and eventually completed.
The above plugins, for which I had to do manual install, were METRO 2.0 and JAXB 2.2
I'm getting this error in eclipse when trying to make new CloudBees project:
Failed to complete ClickStart project provisioning: Read timed out
Does anyone know why this error occurs?
This could be that the clickstart is taking too long to complete - the timeout is set pretty high - of the order of minutes.
Can you run the clickstart from the web interface and see if it works there (or try a different one?)
Any information from the eclipse log would help people diagnose too.
I keep getting an error of org.eclipse.jdi.TimeoutException while waiting for packet -- occurred creating step request.
When that happens I need to restart Eclipse and start all over which is very unproductive.
I tried changing the Timeout settings in options but that didn't seem to help.
Any ideas?
When I start my tomcat in eclipse initially it starts (Green errow - went away - Red appears and consol shows "server startup in 535 ms") in status bar still it says "Starting tomcat v6.0". In some time timeout is done and says server failed to start. I increase timeout to 100 ms from defaultone. Still same issue. Do anyone have any idea?
I tried and applied various solutions given in stackoverflow and other website for this but all failed.
Tomcat starts outside of eclipse.
check netstat and compare no conflicts of any port. (Change all necessary port from eclipse)
Added tomcat-juli.jar (ONE OF THE SOLUTION).
I have not configured a single project yet. Just starting tomcat.
I was able to figure it out. Currently I am not able to remember one application (software) running behind. (install by network admin) for IP/Port related configuration.
First of all this question has been asked at least twice.
I tried several approaches with no effect.
Here's the problem:
When I try to download/update plugins like EclEmma, Eclipse starts to communicate with the repository and that takes about 5 minutes. After that I get an error:
"An error occured while collecting items to be installed
session context was:(...)
Unable to read repository at http: (...)
Read time out
(... for every *.jar)"
What I was trying to fix the problem was running eclipse as an admin (got vista x86 running) and changing the connection properties from native to direct and back. I also tried deleting saved repositories and adding again. No effect at all.
I have no proxy configured and don't need one.
This is getting kind of personal between me and my IDE :D
So I hope you guys can help me out.
Thanks Zoltán (köszi :D), but i found the error last night.
Resolution
After hours of debugging I figured out that AVG Anti-Virus Software blocks the request. After deactivating it for temporarily, Eclipse installed the new software.
In my case timeout was caused by definition of SOCKS proxy... we have proxy.company.com:80 and I incorrectly provided that proxy to all three (HTTP, HTTPS and SOCKS) connection schemas. Removal of proxy from SOCKS resolved the problem
Try to open the internal web browser of Eclipse (Window menu/Show view/Other...), and navigate to the 1) update site url, and 2) to any webpage.
If the latter one is not working, then Eclipse does not have connection to the internet, and you should try to open a new workspace, and try installing from there (possibly something wrong in the workspace settings).
If the second one works, but the first one does not, that suggests that the update site is not working. In this case report to the developers.
I also had this problem (my system: Win7, jdk7, Eclipse Indigo).
I installed jre6, changed my JAVA_HOME, ran eclipse with the following:
eclipse -debug -consolelog -vm 'c:\Program Files\Java\jre6\bin\java.exe'
Install the plugins/updates, then switch back to using jdk7.
Worked for me!
Temporarily disabling AVG firewall fixed the issue for me.
Eclipse then installed the Android plugin.
In my case, adding these lines to eclipse.ini solved the problem
-vmargs (this one was alreayd there)
-Djava.net.preferIPv4Stack=true