Apex Code Development You need to sign in to do that
Don't have an account?
kviswanadha Force.com IDE for Eclipse is not working after updating to Winter 12 - Connection Timeouts
Hello,
I am not able to save my components or refresh my components from Server via Eclipse IDE for Force.com after I updated to Winter 12. I always get Connection Timeout exception.
java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source) at sun.net.www.protocol.https.HttpsClient.New(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source) at com.sforce.ws.transport.JdkHttpTransport.connectRaw(JdkHttpTransport.java:133) at com.sforce.ws.transport.JdkHttpTransport.connectLocal(JdkHttpTransport.java:97) at com.sforce.ws.transport.JdkHttpTransport.connectLocal(JdkHttpTransport.java:92) at com.sforce.ws.transport.JdkHttpTransport.connect(JdkHttpTransport.java:88) at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:94) at com.sforce.soap.metadata.MetadataConnection.describeMetadata(MetadataConnection.java:345) at com.salesforce.ide.core.remote.MetadataStubExt.describeMetadata(MetadataStubExt.java:303) at com.salesforce.ide.core.remote.MetadataStubExt.describeMetadata(MetadataStubExt.java:311) at com.salesforce.ide.core.remote.MetadataStubExt$$FastClassByCGLIB$$9404e285.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:77) at com.salesforce.ide.core.internal.aspects.MetadataOperationsRetryAspect.metadataOperationsRetry(MetadataOperationsRetryAspect.java:22) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:64) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.salesforce.ide.core.remote.MetadataStubExt$$EnhancerByCGLIB$$c1ac1f9d.describeMetadata(<generated>) at com.salesforce.ide.core.services.MetadataService.getDescribeMetadata(MetadataService.java:54) at com.salesforce.ide.core.services.PackageDeployService.adjustDeployOptions(PackageDeployService.java:300) at com.salesforce.ide.core.services.PackageDeployService.deployWork(PackageDeployService.java:264) at com.salesforce.ide.core.services.PackageDeployService.deploy(PackageDeployService.java:144) at com.salesforce.ide.core.services.PackageDeployService.deploy(PackageDeployService.java:127) at com.salesforce.ide.core.services.PackageDeployService.deploy(PackageDeployService.java:111) at com.salesforce.ide.ui.actions.SaveToServerActionController.deploy(SaveToServerActionController.java:132) at com.salesforce.ide.ui.actions.SaveToServerActionController.saveResourcesToServer(SaveToServerActionController.java:114) at com.salesforce.ide.ui.actions.SaveToServerAction$1.execute(SaveToServerAction.java:63) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Please let me know if anyone has the similar problem.
i am running WIndows 7 professional, Eclipse Indigo R1 and have latest Force.com IDE plugin available.
We uploaded a patch. Please update your IDE. If your using the plug-in, eclipse may cache the version. If you don't see 23.0.1, goto Install New Software -> Available Software Sites -> Force.com -> Reload.
All Answers
Which instance are you connecting to?
FYI. we don't support eclipse indigo. Can you please download the latest installer from http://wiki.developerforce.com/index.php/Force.com_IDE_Installation and install that and try.
Thanks.
I am connecting to na9.
ok. Now I uninstalled the Eclipse Indigo and came back to Helios and installed the Force.com IDE Plugin. I am still gettiing connection timeout error. I did configure my proxy to make sure its not the issue.
I am able to connect to Salesforce - I have verified in the User Login History to make sure if I am atleast able to go thourgh the proxy and yes. I am able to. but its failing fetching Force.com Components. - Connection Timeout
I am also having an issue with the Force.com IDE for Eclipse after updating to Winter 12. (I am running Helios on Windows XP). Everything seems to work for my sandboxes but I am unable to pull down the metadata for my production isntance (NA1). I am also unable to deploy to production.
Looks like the new update to Force.com IDE V 23 is having issues. I am not sure what they are but when I reverted back my plugin to install V 20 Force.com IDE, everything worked like a champ.
I am not going to upgrade to 23 unless they figure out what the issue is. I opened a case with salesforce,lets wait and see what they have to say.
I'm also having major issues since upgrading - I can't connect to anything - production or sandboxes. I'm definitely going back to version 20. Very disappointed.
Do you still get timeouts if you refresh an individual component? i.e. Right click on 'classes,' Force.com -> Refresh from server.
dcarmen66, are your connection issues also caused by timeouts?
I couldn't connect to Salesforce at all. I would get messages like "tapp0-api.salesforce.com" not available - I don't remember the exact wording. I tried installing different versions of Eclipse and even the IDE by itself and couldn't get it to work. When I moved back to version 20 everything works fine.
The last I tried with 23.0 from behind Proxy was yesterday evening and was not able to connect - Connection Timeout Error. I reverted back to 20.0 and is working fine for me.
Opened a case with Salesforce on Monday, waiting for them to respond.
Can you post the case #? Would like to follow up on a repro.
thanks,
t
Here you go - Case#06494857. Hoping they come up with some solution quickly. :)
Thanks
Karl.
I'm having the same issue with my sandbox. If I create a brand new force.com project, it actually pulls down the classes. After that though, if I try and refresh or save, it immediately gives me a timeout error. Looks like I need to downgrade.
UPDATE :
I got a call from the Salesforce Support and they told that IDE v 23.0 is still in its beta state. Salesforce R & D is working on the issues and there is no ETA currently available for resolving all issues.
He suggested me to revert back to older version. (guess I did it long back :smileywink:)..
I dont understand if its a beta version, why is it getting installed by default ??
Accordling to the wiki, it isn't Beta - it became GA as of 10/27. Sounds like they messed up.
http://wiki.developerforce.com/page/Force.com_IDE_Release_Notes
http://blogs.developerforce.com/developer-relations/2011/11/force-com-ide-winter-12-update.html
To be clear - this is not a BETA version. This is the GA release. R&D is looking at the timeout issue.
Issue has been identified - we are looking to push the fix either today or Monday.
We uploaded a patch. Please update your IDE. If your using the plug-in, eclipse may cache the version. If you don't see 23.0.1, goto Install New Software -> Available Software Sites -> Force.com -> Reload.
Sorry to say, but 23.0.1 still encounters timeouts if used through a proxy server (our setup at corporate here)
Case 06550548 filed
Has anyone been able to work through a proxy server with Winter 12 IDE plugin? and if so, how?
My proxy settings are:
Eclipse IDE Helios | Window | Preferences | Network Connections
Active provider: Manual
HTTP host=proxy.mydomain.com port = nnnn Provider=manual Auth=false
HTTPS host=<null> port=<null> Provider=manual Auth=false
SOCKS host=<null> port=<null> Provider=manual Auth=false
this had always worked before
I've experienced the same and filed a case with support also. Our company also uses a proxy server, and we continue to experience the time out issue using the 23.0.1 release. Support's initial response was that it must be our proxy server causing the issue, however, I am still able to use Version 20 of the IDE without issue through the same proxy. At this time, my case has been passed around to several support members and no resolution as of yet.
I continue to have issues as well with the Winter 12 update. I was able to get my environment to connect with a proxy by using both manual and native options. I was able to see the schema and download the code (using the default option - didn't try to select components) to create a project but I get connection errors when I attempt to save a class, run a test, perform a refresh from server, and attempt to deploy code from one environment to another.
Going back to version 20 for now.
I'm still having issues. Not exactly timeout issues, but unable to connect. I've opened a case and moved back to version 20.
Unfortunately we have been stuck in the water with this issue and support has been unable to help. Our support rep keeps saying that this is a proxy issue that needs to be addressed by my corporate network group. Funny, though, that version 20 still works without issue. Luckily we were able to revert back to the prior release on one of our development machines.
same here -- my support case has been referred to Tier 3 and I was asked to provide a stack trace. I too have reverted to Version 20
The proxy issue appears to be different then the one we released a patch for. We got the traces and are looking into it. No ETA at this point.
Is there any update or ETA for when this will be fixed. It has stopped our entire development team from upgrading to the latest version.
After speaking with Tier 3 support, I found that the ETA for an update release to resolve the issue is December 23.
I'm using the stand alone Force.com IDE v 23 and it is having major problems! It's pretty much unusable. SF support says they are working on a fix, but I can't wait. Where do I get v 20 to revert back?
Its a lot easy to use Eclipse Plugin and select on Show All Versions in the installation page and select the V 20 instead of the latest version. and install it.
If you are using Force.com IDE, the updates are controller by Pulse Explorer. you can try going to Pulse Explorer and add local site, but I dont if that works.
Thanks for this bit of advice. I had not noticed the option "Show only the latest versions of available software" previously in Eclipse and SF support said there was no way to install a prior version during a new installation of Eclipse. Deselecting the option allows you to install one of the prior versions.
Any update on this? Has it been fixed? I don't really want to go through the hassle of updating to test myself if I have to immediately downgrade again.
I had the problem initially and the latest version of the IDE seems to fix the problem. I've been using it for a couple of weeks now and have had no problem.
The latest IDE for Eclipse release (23.0.2.201201091635) seems to have resolved the issue I was experiencing. I just loaded it on a dev machine, ran a few tests of updating and adding classes, and no errors were generated.