spring-cloud-config: Setting timeout value for git repo does not have any effect

We are running with the Edgware SR2 build.

We have set the spring.cloud.config.server.git.timeout value (which is seconds for the unit) to 10 for one release and 120 for another. It does not seem to have any effect on the actual timeout. We see git response timeout errors on occasion. In every case, it reports timeout after 5 seconds:

Caused by: java.io.InterruptedIOException: Read timed out after 5,000 ms at org.eclipse.jgit.util.io.TimeoutInputStream.readTimedOut(TimeoutInputStream.java:141) at
 org.eclipse.jgit.util.io.TimeoutInputStream.read(TimeoutInputStream.java:114) at
 org.eclipse.jgit.util.IO.readFully(IO.java:246) at
 org.eclipse.jgit.transport.PacketLineIn.readLength(PacketLineIn.java:186) at
 org.eclipse.jgit.transport.PacketLineIn.readString(PacketLineIn.java:138) at 
 org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefsImpl(BasePackConnection.java:195) at
 org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefs(BasePackConnection.java:176)

How can we change the timeout? Is this broken in the Edgware SR2 build? Are there separate settings for connection and response timeouts perhaps?

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 25 (23 by maintainers)

Most upvoted comments

For anyone interested in this topic:

I was able to affect the git read timeout value when using https for the git repo connection protocol, but only by specifying timeout on each git repo (in addition to the value for the default repo).


spring:
  cloud:
    config:
      server:
        git:
          # Connection timeout in seconds. (Also the read timeout when using https.)
          timeout: 10

          uri : https://someuri
          repos:

            Service:
              pattern: '*Service'
              searchPaths: Service/{applicaton}
              timeout: 10
              uri : https://someotheruri

Additional Notes:

  • I am using Edgware SR5 and spring boot 1.5.14.RELEASE.
  • The timeout setting is still being ignored for ssh, even when setting it on each repo, as expected based on the other information in this conversation.