Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Problem connecting to the internet with GGTS 3.1.0.RELEASE

  1. #11
    Join Date
    Jan 2012
    Posts
    11

    Default

    Hi all,

    I'm having the same problem with Windows 7 64 bits.

    The STS loads the proxy configuration, but it doesn't keep user and password. So, i can't work with STS behind the proxy in the corporative network.
    Last edited by manuelcr; Feb 3rd, 2013 at 06:50 AM.

  2. #12
    Join Date
    May 2010
    Posts
    398

    Default

    Hi Warpcore,

    I'm not sure how to help you further. Right now I am running a GGTS 3.2.0.M2 instance on a 32 bit Ubuntu 10.04. As far as I can tell the Secure Storage works fine for me, but since I'm not behind a proxy I don't know if *that* would work for me.

    My sense from going back through all the posts in this thread is that Secure Storage itself is actually working ok for you (with the 'UI provider' enabled).

    I don't seem to have any other options myself than to use the 'UI provider'. I think this means you have to enter the master password once per Eclipse/GGTS session.

    I don't think that is the problem. Rather it seems maybe some wires are getting crossed with the Eclipse network connector libraries actually using the info from secure storage to configure your proxies.

    I fear sending you on another wild-goose chase, but... have you tried a 'plain' instance of Eclipse. It would be interesting to determine if a plain Eclipse also has similar issues when you configure proxies the same way.

    If it does then I guess we are most likely dealing with some Eclipse bug. If not, then something in GGTS is messing this up.

    Thanks for your patience and sorry for all the trouble you are having with this.

    Kris
    Kris De Volder -- SpringSource

  3. #13
    Join Date
    Jan 2013
    Posts
    9

    Default

    Kris,

    thanks for getting back. I tried installing the Juno Standard SDK (4.2.1). Then I configured my network connection both with or without secure storage. The behavior is pretty much the same. Here are the last lines of the error log when trying to search for updates:

    Code:
    !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2013-02-05 10:25:03.251
    !MESSAGE Unable to read repository at http://download.eclipse.org/releases/juno/201209280900/content.jar.
    !STACK 0
    java.net.SocketTimeoutException: Read timed out
            at java.net.SocketInputStream.read(SocketInputStream.java:155)
            at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
            at java.io.BufferedInputStream.read1(BufferedInputStream.java:267)
            at java.io.BufferedInputStream.read(BufferedInputStream.java:324)
            at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:658)
            at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:607)
            at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:734)
            at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:607)
            at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1140)
            at org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveFileTransfer.getDecompressedStream(UrlConnectionRetrieveFileTransfer.java:542)
            at org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveFileTransfer.openStreams(UrlConnectionRetrieveFileTransfer.java:312)
            at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879)
            at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570)
            at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
            at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422)
            at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:355)
            at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
            at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
            at org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:345)
            at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:208)
            at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:66)
            at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:88)
            at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
            at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:758)
            at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651)
            at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
            at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
            at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:165)
            at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:105)
            at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
            at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
            at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:758)
            at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651)
            at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
            at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
            at org.eclipse.equinox.p2.engine.ProvisioningContext.loadMetadataRepository(ProvisioningContext.java:211)
            at org.eclipse.equinox.p2.engine.ProvisioningContext.getLoadedMetadataRepositories(ProvisioningContext.java:194)
            at org.eclipse.equinox.p2.engine.ProvisioningContext.getMetadata(ProvisioningContext.java:275)
            at org.eclipse.equinox.internal.p2.director.SimplePlanner.updatesFor(SimplePlanner.java:777)
            at org.eclipse.equinox.p2.operations.UpdateOperation.updatesFor(UpdateOperation.java:143)
            at org.eclipse.equinox.p2.operations.UpdateOperation.computeProfileChangeRequest(UpdateOperation.java:180)
            at org.eclipse.equinox.p2.operations.UpdateOperation$1.run(UpdateOperation.java:324)
            at org.eclipse.equinox.internal.p2.operations.SearchForUpdatesResolutionJob.runModal(SearchForUpdatesResolutionJob.java:37)
            at org.eclipse.equinox.p2.operations.ProfileChangeOperation.resolveModal(ProfileChangeOperation.java:115)
            at org.eclipse.equinox.internal.p2.ui.sdk.UpdateHandler.doPostLoadBackgroundWork(UpdateHandler.java:49)
            at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:87)
            at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
            at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
    !SESSION 2013-02-05 10:25:23.054 -----------------------------------------------
    eclipse.buildId=M20120914-1800
    java.fullversion=J2RE 1.5.0 IBM J9 2.3 Linux amd64-64 j9vmxa6423-20111019 (JIT enabled)
    J9VM - 20111017_92807_LHdSMr
    JIT  - 20110916_20782_r8
    GC   - 20110524_AA
    BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE
    Command-line arguments:  -os linux -ws gtk -arch x86_64
    
    !ENTRY org.eclipse.core.net 1 0 2013-02-05 10:25:33.111
    !MESSAGE System property http.proxyHost is not set but should be webproxy.
    
    !ENTRY org.eclipse.core.net 1 0 2013-02-05 10:25:33.113
    !MESSAGE System property http.proxyPort is not set but should be 8080.
    
    !ENTRY org.eclipse.core.net 1 0 2013-02-05 10:25:33.115
    !MESSAGE System property https.proxyHost is not set but should be webproxy.
    
    !ENTRY org.eclipse.core.net 1 0 2013-02-05 10:25:33.115
    !MESSAGE System property https.proxyPort is not set but should be 8080.
    
    !ENTRY org.eclipse.core.net 1 0 2013-02-05 10:25:33.119
    !MESSAGE System property https.proxyHost is not set but should be webproxy.
    
    !ENTRY org.eclipse.core.net 1 0 2013-02-05 10:25:33.119
    !MESSAGE System property https.proxyPort is not set but should be 8080.
    In addition I get the following messages on the shell where eclipse was started:

    Code:
    05.02.2013 10:20:01 org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
    INFO: ntlm authentication scheme selected
    05.02.2013 10:20:01 org.apache.commons.httpclient.HttpMethodDirector processProxyAuthChallenge
    INFO: No credentials available for NTLM <any realm>@webproxy:8080
    05.02.2013 10:20:39 org.apache.commons.httpclient.HttpConnection releaseConnection
    WARNUNG: HttpConnectionManager is null.  Connection cannot be released.
    05.02.2013 10:22:02 org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
    INFO: ntlm authentication scheme selected
    05.02.2013 10:22:02 org.apache.commons.httpclient.HttpMethodDirector processProxyAuthChallenge
    INFO: No credentials available for NTLM <any realm>@webproxy:8080
    05.02.2013 10:22:43 org.apache.commons.httpclient.HttpConnection releaseConnection
    WARNUNG: HttpConnectionManager is null.  Connection cannot be released.
    05.02.2013 10:23:40 org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
    INFO: ntlm authentication scheme selected
    05.02.2013 10:23:40 org.apache.commons.httpclient.HttpMethodDirector processProxyAuthChallenge
    INFO: No credentials available for NTLM <any realm>@webproxy:8080
    05.02.2013 10:25:19 org.apache.commons.httpclient.HttpConnection releaseConnection
    WARNUNG: HttpConnectionManager is null.  Connection cannot be released.
    Does this help ?

    I tried the STS 2.9.2 network connection and it still works(!)

    Cheers,
    Robert

  4. #14
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    1,637

    Default

    Hey Robert!

    I am kind of in the same position as Kris, not experiencing the problem myself. But it is quite strange that it worked with STS 2.9.2, but doesn't work anymore with GGTS 3.1.0 or the latest Eclipse installation. To further identify the issue, we could try additional cases:

    #1: does this work again with Eclipse Juno SDK 4.2.2 (the latest RC builds)?
    #2: you could use GGTS 3.1.0.RELEASE on top of Eclipse 3.7 from here:
    http://download.springsource.com/rel...nux-gtk.tar.gz
    http://download.springsource.com/rel...-x86_64.tar.gz

    That GGTS build is using the same Eclipse version as 2.9.2. We don't extensively test those older builds, therefore they aren't promoted anymore as preferred downloads, but in your case it would make sense to give it a try, I think.

    HTH,
    Martin
    Martin Lippert
    SpringSource, a division of VMware
    SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/martinlippert

  5. #15
    Join Date
    Jan 2013
    Posts
    9

    Default

    Hi Martin,

    option #2 did not work for me. Still having the same problems. I could not find a download for option #1 but instead I downloaded eclipse SDK 4.3M4: No success. But what I got is the following output on my shell when trying to search for updates:

    Code:
    06.02.2013 11:24:08 org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
    INFO: ntlm authentication scheme selected
    06.02.2013 11:24:08 org.apache.commons.httpclient.HttpMethodDirector processProxyAuthChallenge
    INFO: No credentials available for NTLM <any realm>@webproxy:8080
    Could this point to something more specific ?


    Cheers,
    Robert

  6. #16
    Join Date
    May 2010
    Posts
    398

    Default

    Hi Robert,

    All this proxy stuff is a bit foreign to me... and it is indeed worrysome that option #2 doesn't work for you where STS 2.9.2 on top of Eclipse 3.7 did work. That suggests there's an issue with GGTS of some sort that didn't exist before. If we can figure out what the problem is we should and try to fix it...

    But... as the root problem still stands undiagnosed.

    I did a bit of googling based on that NTLM error message and found this:

    http://www.thinkplexx.com/learn/arti...ion-from-linux
    http://cntlm.sourceforge.net/

    Perhaps setting up cntlm to take care of the proxying outside of GGTS may work.
    Basically it looks like you can use 'cntlm' to create a more standard kind of proxy on localhost to bypass the Corporate ntlm Microsoft proxy authentication.

    Although that doesn't really solve the underlying issue in GGTS, maybe if it work, it might be a way for you to at least get working again.

    Kris
    Kris De Volder -- SpringSource

  7. #17
    Join Date
    Jan 2013
    Posts
    9

    Thumbs up

    Hi Kris,

    sorry for getting back so late. I was busy with other things, but I have good news. IT WORKS

    Using cntlm as tunnel for our NTLM Proxy did the trick. I am now able to connect to the repositories and see the RSS feeds. So it really seems to be a bug in GGTS because my older version of STS is still able to connect to our proxy directly.

    Anyways, thanks for pointing me to the right direction.

    I will add this information to the Grails JIRA database, just in case someone else is having the same issues.


    Cheers,
    Robert

  8. #18
    Join Date
    May 2010
    Posts
    398

    Default

    I'm glad you got things working.

    > I will add this information to the Grails JIRA database ...

    Thanks Robert, that would be great!

    Kris
    Kris De Volder -- SpringSource

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •