SonarQube Weird behavior - tasks are cancelled randomly

Must-share information (formatted with [Markdown] (Markdown Reference)):
Which versions are you using (SonarQube, Scanner, Plugin, and any relevant extensions)?
What are you trying to achieve?
What have you tried so far to achieve this?

First, i would appreciate your time reading and helping us in this trouble.

Installation:
Upgrade from SonarQube 8.5.3 to SonarQube 8.9.6 LTS (Enterprise)
We used (helm-chart-sonarqube/charts/sonarqube at master · SonarSource/helm-chart-sonarqube · GitHub) helm chart (LTS version) introduced on sonarqube.org to install the 8.9 on OpenShift 4.

We connect to our SQL server database via JDBC. We upgraded our database when SonarQube ran for the first time. it took maybe 10 minutes.

Everything works like our old SonarQube (8.5.1).

The problem
The annoying problem is when we tested SonarQube with some of our test teams, randomlysome of their tasks get cancelled and some get succeeded.

In the following, the picture displays how random the tasks are being completed or cancelled from the maven project I have locally. There is one anonymous submitter and this is when I restart the POD on OpenShift. It seems like they are in the queue. However, they all don’t get executed.

In the following, the picture shows again how random the tasks are being completed or cancelled but this time from our bamboo pipeline. The same script on the bamboo pipeline works perfectly with our OLD SonarQube 8.5.1. There are build on push and pull request decoration records in this picture. Again anonymous records are for when i restarted the POD.

both projects, the local one and the one built by bamboo are small projects, less than 150 lines of codes

I checked some old SonarQube topics in this forum, it seems people connected two instances to one database. This is not true in our case because we cloned the Prod database into a different instance and nobody is aware of this instance.
However, in the following you can see the connections to the database:

More importantly, the logs are set to debug and i cannot see the cancelled records in the logs!! only the successful records can be found. For instance, in the following:

2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.s.d.purge.PurgeDao] <- Purge stale branches
2022.06.30 08:03:43 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.s.ComputationStepExecutor] Purge db | status=SUCCESS | time=111ms
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.p.s.IndexAnalysisStep] Call org.sonar.server.measure.index.ProjectMeasuresIndexer@33491766
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.MainClientExec] [exchange: 3144] start execution
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAddCookies] CookieSpec selected: default
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] Re-using cached 'basic' auth scheme for http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] No credentials for preemptive authentication
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3144] Request connection for {}->http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection request: [route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection leased: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3144] Connection allocated: CPoolProxy{http-outgoing-0 [ACTIVE]}
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Attempt 1 to execute request
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Target auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Proxy auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> POST /_bulk?timeout=1m HTTP/1.1
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Length: 1238
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Type: application/json
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Host: localhost:9001
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Connection: Keep-Alive
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> User-Agent: elasticsearch-java/7.16.0-SNAPSHOT (Java/11.0.11)
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> X-Elastic-Client-Meta: es=7.16.0-SNAPSHOT,jv=11,t=7.16.0-SNAPSHOT,hc=4.1.4,kt=1.4
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] produce content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Request completed
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-length: 243
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Response received HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Consume content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3144] Connection can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3144] Response processed
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3144] releasing connection
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://localhost:9001] can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.MainClientExec] [exchange: 3145] start execution
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAddCookies] CookieSpec selected: default
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] Re-using cached 'basic' auth scheme for http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] No credentials for preemptive authentication
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3145] Request connection for {}->http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection request: [route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection leased: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3145] Connection allocated: CPoolProxy{http-outgoing-0 [ACTIVE]}
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Attempt 1 to execute request
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Target auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Proxy auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> POST /projectmeasures/_refresh HTTP/1.1
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Length: 0
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Host: localhost:9001
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Connection: Keep-Alive
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> User-Agent: elasticsearch-java/7.16.0-SNAPSHOT (Java/11.0.11)
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> X-Elastic-Client-Meta: es=7.16.0-SNAPSHOT,jv=11,t=7.16.0-SNAPSHOT,hc=4.1.4,kt=1.4
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Request completed
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-length: 49
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Response received HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Consume content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3145] Connection can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3145] Response processed
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3145] releasing connection
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://localhost:9001] can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.p.s.IndexAnalysisStep] Call org.sonar.server.component.index.ComponentIndexer@d1c0b5c
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.MainClientExec] [exchange: 3146] start execution
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAddCookies] CookieSpec selected: default
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] Re-using cached 'basic' auth scheme for http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] No credentials for preemptive authentication
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3146] Request connection for {}->http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection request: [route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection leased: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3146] Connection allocated: CPoolProxy{http-outgoing-0 [ACTIVE]}
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Attempt 1 to execute request
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Target auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Proxy auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> POST /_bulk?timeout=1m HTTP/1.1
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Length: 350
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Type: application/json
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Host: localhost:9001
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Connection: Keep-Alive
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> User-Agent: elasticsearch-java/7.16.0-SNAPSHOT (Java/11.0.11)
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> X-Elastic-Client-Meta: es=7.16.0-SNAPSHOT,jv=11,t=7.16.0-SNAPSHOT,hc=4.1.4,kt=1.4
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] produce content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Request completed
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-length: 239
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Response received HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Consume content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3146] Connection can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3146] Response processed
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3146] releasing connection
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://localhost:9001] can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.MainClientExec] [exchange: 3147] start execution
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAddCookies] CookieSpec selected: default
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] Re-using cached 'basic' auth scheme for http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] No credentials for preemptive authentication
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3147] Request connection for {}->http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection request: [route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection leased: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3147] Connection allocated: CPoolProxy{http-outgoing-0 [ACTIVE]}
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Attempt 1 to execute request
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Target auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Proxy auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> POST /components/_refresh HTTP/1.1
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Length: 0
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Host: localhost:9001
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Connection: Keep-Alive
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> User-Agent: elasticsearch-java/7.16.0-SNAPSHOT (Java/11.0.11)
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> X-Elastic-Client-Meta: es=7.16.0-SNAPSHOT,jv=11,t=7.16.0-SNAPSHOT,hc=4.1.4,kt=1.4
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Request completed
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-length: 49
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Response received HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Consume content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3147] Connection can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3147] Response processed
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3147] releasing connection
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://localhost:9001] can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.p.s.IndexAnalysisStep] Call org.sonar.server.issue.index.IssueIndexer@541196d9
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.MainClientExec] [exchange: 3148] start execution
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAddCookies] CookieSpec selected: default
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] Re-using cached 'basic' auth scheme for http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] No credentials for preemptive authentication
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3148] Request connection for {}->http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection request: [route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection leased: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3148] Connection allocated: CPoolProxy{http-outgoing-0 [ACTIVE]}
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Attempt 1 to execute request
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Target auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Proxy auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> POST /_bulk?timeout=1m HTTP/1.1
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Length: 35787
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Type: application/json
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Host: localhost:9001
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Connection: Keep-Alive
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> User-Agent: elasticsearch-java/7.16.0-SNAPSHOT (Java/11.0.11)
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> X-Elastic-Client-Meta: es=7.16.0-SNAPSHOT,jv=11,t=7.16.0-SNAPSHOT,hc=4.1.4,kt=1.4
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] produce content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Request completed
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-length: 7473
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Response received HTTP/1.1 200 OK
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Consume content
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3148] Connection can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3148] Response processed
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3148] releasing connection
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://localhost:9001] can be kept alive indefinitely
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.MainClientExec] [exchange: 3149] start execution
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAddCookies] CookieSpec selected: default
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] Re-using cached 'basic' auth scheme for http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.c.p.RequestAuthCache] No credentials for preemptive authentication
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3149] Request connection for {}->http://localhost:9001
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection request: [route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection leased: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:43 DEBUG ce[AYGzox-ipVI49LoZwL_7][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3149] Connection allocated: CPoolProxy{http-outgoing-0 [ACTIVE]}
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Attempt 1 to execute request
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Target auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Proxy auth state: UNCHALLENGED
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> POST /issues/_refresh HTTP/1.1
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Content-Length: 0
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Host: localhost:9001
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> Connection: Keep-Alive
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> User-Agent: elasticsearch-java/7.16.0-SNAPSHOT (Java/11.0.11)
2022.06.30 08:03:43 DEBUG ce[][o.a.http.headers] http-outgoing-0 >> X-Elastic-Client-Meta: es=7.16.0-SNAPSHOT,jv=11,t=7.16.0-SNAPSHOT,hc=4.1.4,kt=1.4
2022.06.30 08:03:43 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Request completed
2022.06.30 08:03:44 DEBUG ce[][o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2022.06.30 08:03:44 DEBUG ce[][o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2022.06.30 08:03:44 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2022.06.30 08:03:44 DEBUG ce[][o.a.http.headers] http-outgoing-0 << content-length: 49
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Response received HTTP/1.1 200 OK
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Consume content
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3149] Connection can be kept alive indefinitely
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.MainClientExec] [exchange: 3149] Response processed
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 3149] releasing connection
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://localhost:9001] can be kept alive indefinitely
2022.06.30 08:03:44 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://localhost:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.s.ComputationStepExecutor] Index analysis | status=SUCCESS | time=321ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.s.ComputationStepExecutor] Update need issue sync for branch | status=SUCCESS | time=7ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.s.ComputationStepExecutor] Send issue notifications | newIssuesNotifs=0 | newIssuesDeliveries=0 | myNewIssuesNotifs=0 | myNewIssuesDeliveries=0 | changesNotifs=0 | changesDeliveries=0 | status=SUCCESS | time=71ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.s.ComputationStepExecutor] Publish task results | status=SUCCESS | time=0ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.s.ComputationStepExecutor] Trigger refresh of Portfolios and Applications | refreshesAPP=0 | refreshesVW=0 | status=SUCCESS | time=105ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Webhooks | globalWebhooks=0 | projectWebhooks=0 | status=SUCCESS | time=4ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Pull Request decoration | status=SUCCESS | time=0ms
2022.06.30 08:03:44 INFO  ce[AYGzox-ipVI49LoZwL_7][o.s.c.t.CeWorkerImpl] Executed task | project=com.sonarqube.testt | type=REPORT | id=AYGzox-ipVI49LoZwL_7 | submitter=v006289 | status=SUCCESS | time=1769ms

In the above log file, which is copied from the end of the CE log file, only the ID of AYGzox-ipVI49LoZwL_7 is logged which was the last successful task, shown in the pictures earlier. The failed ones cannot be found in the CE log file. I really don’t know what to do!!!

I need your urgent expert assistance.
Thanks!

x

It sure looks like two different hosts are connecting to the database – sonarqube-21-l9txp and sonarqube-sonarqube-lts-0.

SonarQube can’t magically cause two different hosts to be connected to the database – do you know why there are these two separate hosts?

2 Likes

Hi Colin,

Thanks for your super fast response. I am really hopefull this would be the case.
I am going to check that with out database team and will come back here to give you the results.

Thank you, Colin.

I was so sure that no one was connected to our SQL server, but I was wrong. We moved the database to an isolated instance, and now it works like a charm.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.