Jenkins trying to pull last sonar state when browsing a job, making jenkins TMOUT

[bofus (Mauro Boffito)]

Hi Community!
I run into an issue that took me a while to find the cause. A user reported that was unable to access a jenkins’s job via its browser, effectively the job was timing out. Checking Jenkins logs I found out:

Error fetching project information
java.net.SocketTimeoutException: connect timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:607)
	at okhttp3.internal.platform.Platform.connectSocket(Platform.java:124)
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:221)
	at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:147)
	at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:192)
	at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:121)
	at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:100)
	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)
	at okhttp3.RealCall.execute(RealCall.java:69)
	at org.sonarqube.ws.client.HttpConnector.doCall(HttpConnector.java:188)
Caused: java.lang.IllegalStateException: Fail to request https://sonarqube-legacy.url/api/ce/task?id=AYaANsjxbLEQIcp9XcS0

Searching a bit on google I found out that apparently when you browse a job or API query it, it will try to get the last sonar result from the build. Since this instance was decommission I believe its whats causing the problems. The question is, anyone knows how can I bypass that “check” jenkins does against sonarqube?

This was reported here https://issues.jenkins.io/browse/JENKINS-54583

• Jenkins Sonar Plugin Version: 2.14
• Jenkins Instance: 2.249.1

Best Regards!

[ganncamp (G Ann Campbell)]

Hi,

Can you try removing the SonarQube analysis from the job configuration?

 
Ann

[bofus (Mauro Boffito)]

Hi Ann,
I think I solved it a couple of hours ago as you mention. I had to remove the sonar analysis lines from the last build of the job, like:

<hudson.plugins.sonar.action.SonarMarkerAction plugin="sonar@2.14"/>
    <hudson.plugins.sonar.action.SonarAnalysisAction plugin="sonar@2.14">
      <installationName>Sonar01</installationName>
      <installationUrl>https://sonarqube-legacy.url</installationUrl>
      <ceTaskId>AYaANsjxbLEQIcp9XcS0</ceTaskId>
      <url>https://sonarqube-legacy.url/dashboard?id=some.parent.jobt</url>
      <serverUrl>https://sonarqube-legacy.url</serverUrl>
      <isNew>true</isNew>
      <isSkipped>false</isSkipped>
    </hudson.plugins.sonar.action.SonarAnalysisAction>

After removing such line I had to reload the Jenkins job, I did it via console script with

Jenkins j = Jenkins.get()
def job = j.getItemByFullName("PROJECT_NAME")

job?.doReload()

That did the trick!
Thanks for your support.