"The bridge server is unresponsive" error while scanning Typescript project

pvujic · February 16, 2024, 10:55am

We’ve got the same issue since yesterday on bitbucket.


`10:06:27.672 DEBUG: Found file: /opt/atlassian/pipelines/agent/build/modules/ps_facetedsearch/package.json`
...

`10:06:29.318 INFO: Analyzed 0 file(s) with current program`

30482

`10:06:29.322 INFO: Creating TypeScript program`

30483

`10:06:29.322 INFO: TypeScript configuration file /opt/atlassian/pipelines/agent/build/tests/UI/tsconfig.json`

30484

`10:06:40.030 INFO: 0/49 files analyzed, current file: /opt/atlassian/pipelines/agent/build/themes/reformam/_dev/js/components/block-cart.js`

30485

`10:06:50.252 INFO: 0/49 files analyzed, current file: /opt/atlassian/pipelines/agent/build/themes/reformam/_dev/js/components/block-cart.js`

30486

`10:06:51.745 DEBUG: The worker thread exited with code 1`

30487

`10:07:00.766 INFO: 0/49 files analyzed, current file: /opt/atlassian/pipelines/agent/build/themes/reformam/_dev/js/components/block-cart.js`

30488

`10:07:10.766 INFO: 0/49 files analyzed, current file: /opt/atlassian/pipelines/agent/build/themes/reformam/_dev/js/components/block-cart.js`
...

`10:11:20.781 INFO: 0/49 files analyzed, current file: /opt/atlassian/pipelines/agent/build/themes/reformam/_dev/js/components/block-cart.js`

30514

`10:11:29.329 ERROR: Failure during analysis`

30515

`java.lang.IllegalStateException: The bridge server is unresponsive`

30516

`	at org.sonar.plugins.javascript.bridge.BridgeServerImpl.request(BridgeServerImpl.java:403)`

30517

`	at org.sonar.plugins.javascript.bridge.BridgeServerImpl.createProgram(BridgeServerImpl.java:490)`

30518

`	at org.sonar.plugins.javascript.bridge.AnalysisWithProgram.analyzeFiles(AnalysisWithProgram.java:79)`

30519

`	at org.sonar.plugins.javascript.bridge.JsTsSensor.analyzeFiles(JsTsSensor.java:132)`

30520

`	at org.sonar.plugins.javascript.bridge.AbstractBridgeSensor.execute(AbstractBridgeSensor.java:79)`

30521

`	at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(AbstractSensorWrapper.java:62)`

30522

`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:75)`

30523

`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.lambda$execute$1(ModuleSensorsExecutor.java:48)`

30524

`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.withModuleStrategy(ModuleSensorsExecutor.java:66)`

30525

`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:48)`

30526

`	at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:64)`

30527

`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`

30528

`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`

30529

`	at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:192)`

30530

`	at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:188)`

30531

`	at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:159)`

30532

`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`

30533

`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`

30534

`	at org.sonar.scanner.bootstrap.ScannerContainer.doAfterStart(ScannerContainer.java:397)`

30535

`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`

30536

`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`

30537

`	at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(GlobalContainer.java:125)`

30538

`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`

30539

`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`

30540

`	at org.sonar.batch.bootstrapper.Batch.doExecute(Batch.java:57)`

30541

`	at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:51)`

30542

`	at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:46)`

30543

`	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)`

30544

`	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)`

30545

`	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)`

30546

`	at java.base/java.lang.reflect.Method.invoke(Method.java:568)`

30547

`	at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)`

30548

`	at jdk.proxy1/jdk.proxy1.$Proxy0.execute(Unknown Source)`

30549

`	at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:189)`

30550

`	at org.sonarsource.scanner.api.EmbeddedScanner.execute(EmbeddedScanner.java:138)`

30551

`	at org.sonarsource.scanner.cli.Main.execute(Main.java:126)`

30552

`	at org.sonarsource.scanner.cli.Main.execute(Main.java:81)`

30553

`	at org.sonarsource.scanner.cli.Main.main(Main.java:62)`

30554

`Caused by: java.net.http.HttpTimeoutException: request timed out`

30555

`	at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:571)`

30556

`	at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:123)`

30557

`	at org.sonar.plugins.javascript.bridge.BridgeServerImpl.request(BridgeServerImpl.java:398)`

30558

`	... 37 common frames omitted`

30559

``

30560

`10:11:29.330 DEBUG: The bridge server shut down`

victor.diez · February 16, 2024, 11:34am

Hi @Brandon_Lee,

I will send you a private message. You can share it there.

Cheers,
Victor

victor.diez · February 16, 2024, 11:36am

Hello @pvujic,

did you try increasing the docker and Node.js memory as shown here?

Brandon_Lee · February 19, 2024, 3:03am

Hi Victor

Here’s the log that you requested

Cheers
Brandon

pipelineLog-{7654d0d1-3cce-41dc-b85e-15e74024e4e0}.txt.zip (453 KB)

victor.diez · February 19, 2024, 10:43am

Hi @Brandon_Lee,

did you try increasing memory for Docker service in the pipelines.yml?

definitions:
  services:
    docker:
      memory: 4096

pvujic · February 19, 2024, 11:07am

4096 seems to have given me issues on bitbucket, seems that with 3072 works great now.

Thank you!

Brandon_Lee · February 19, 2024, 3:21pm

Then I got an error from Bitbucket.

RishabhA · February 20, 2024, 5:30am

Hi Team,

Im on jenkins pipeline and im not using any node.js, you mean shall need to increase the memory of my instances like where my jenkins is runing im using free tier aws account for my client using 1gB 1vcpu

I resume today as i was not well I will try to increase sonar memory im trying figure it out how I can do

Chernomirdin · February 21, 2024, 1:05pm

Hello @victor.diez
Well, everything was going well with the solution you proposed.
Until a few days ago, i started getting another Error.

I added the pipeline log in the attachments

pipelineLog-{047a85ed-aa24-4249-9ddf-b0431edb3470}.txt (28.4 KB)

andrelgomes · February 21, 2024, 9:51pm

Our team did not get reliable pipelines passing even with the increase in docker memory, especially with pipelines running in parallel. Creating a custom docker service to reserve memory for sonarcloud-scan was the only way we got consistent passing pipelines. With this solution, we did not need to increase our default docker service for other steps.

definitions:
  services:
    docker:
      memory: 3072
    docker-4g:
      memory: 4096
      type: docker
...
  steps:
      - step: &sonarcloud-scan
          size: 2x
          max-time: 20 // Helps stops running off scans
          services:
             - docker-4g
          script:
              ...
              - pipe: sonarsource/sonarcloud-scan:2.0.0
                  variables:
                  EXTRA_ARGS: '-Dsonar.javascript.node.maxspace=4096'

Leticia_Sant_anna · February 22, 2024, 9:08pm

Hi guys, I’m having the same problem since a couple weeks ago, I already tried the docker memory solution but broken my pipeline

pipe: sonarsource/sonarcloud-scan:2.0.0
variables:
SONAR_SCANNER_OPTS: -Xmx4096m
EXTRA_ARGS: -Dsonar.javascript.node.maxspace=4096 -Dsonar.sourceEncoding=UTF-8

This hint also don’t work

Follow the pipeline log for sonar step. Could someone help me? It’s a project in React + TypeScript
The problem start happen after I change for 2.0 version of sonarScan. If you need the document with debug of pipeline is here:
pipelineLog-{2a966f82-0248-450e-80d3-3e92abdee32e}.txt (12.2 MB)

Renatas · March 7, 2024, 9:21am

Hi, my team are also experiencing the same issues. Our project is with Vue / TypeScript.
Increasing docker memory from 3072 to 4096 gives me the same error like the above, and the pipelines don’t run.
I’ve also tried the proposed solutions but they didn’t help:

      - pipe: sonarsource/sonarcloud-scan:2.0.0
        variables:
          SONAR_SCANNER_OPTS: -Xmx4096m
          EXTRA_ARGS: -Dproject.settings=sonar-project.properties -Dsonar.sourceEncoding=UTF-8 -Dsonar.verbose=true -Dsonar.javascript.node.maxspace=4096
      - pipe: sonarsource/sonarcloud-quality-gate:0.1.6

Could I share my debug logs with someone privately?

whiteninja76 · March 19, 2024, 2:15pm

IS there an internal reference/bug that we can track to see when this issue is resolved?
Increasing(doubling) the allocated memory in bitbucket for the step seems a workaround and not a fix, Not to mention it burns thought the bitbucket bill…

victor.diez · March 19, 2024, 3:56pm

We have identified the issue for Vue projects, and we will disable type-checking for them. The next release will solve this issue for Vue, expected in production in ~10 days. If you are facing this issue on non-Vue projects, we have not yet identified any major issue, aside from an expected increase of memory from Typescript itself.

whiteninja76 · March 19, 2024, 4:20pm

Yes it for a Terraform Cdktf project in typescript. started noticing the issues around the start of the year with the bitbucket pipeline

hummer182 · April 3, 2024, 1:08pm

I was facing the same issue while trying to run this over bitbucket pipelines, only for the project in JS/TS. I tried to run it locally and it worked. My workaround to get this working on bitbucket pipelines was stop using pipe and used sonnar-scanner-cli image instead:

    - step: &test-step
        name: SonarQube analysis
        image: sonarsource/sonar-scanner-cli:5
        script:
          - sonar-scanner

hash3liZer · April 24, 2024, 7:23am

Hi Marco. Thanks for the suggestion. I did the same and surprisngly it worked.

steps:
    - step:
        name: SonarQube analysis
        image: sonarsource/sonar-scanner-cli:5
        memory: 4096
        caches:
          - sonar
        clone:
          depth: full
        script:
          - sonar-scanner -Dsonar.projectKey=${SONAR_PROJECT_KEY} -Dsonar.sources=. -Dsonar.host.url=${SONAR_HOST_URL} -Dsonar.login=${SONAR_TOKEN} -Dsonar.javascript.node.maxspace=4096 -Dsonar.sourceEncoding=UTF-8

Renatas · May 7, 2024, 7:35am

The sonarsource/sonar-scanner-cli:5 image doesn’t solve it for me.
Still getting the same java.lang.IllegalStateException: The bridge server is unresponsive error

balaji_g · September 10, 2024, 7:16am

@Colin @victor.diez we are also facing same issue suddenly we are running sonar scanner through gitlab pipeline, will increasing the memory as suggested above will fix the issue ?

Colin · September 10, 2024, 8:33am

Hey @balaji_g

We sure hope so! If you face problems, please open a new thread with logs, pipeline config, etc.