Multiple instance of JDTLS servers running

[saitharun14]

Hi there,

I have recently started using neovim and I'm noobie when it come to setting up the configs. I'm trying to setup the nvim-jdtls for my work and I'm getting the following warning when I'm opening a java project "Multiple LSP clients found that support java.project.isTestFile you should have at most one JDTLS server running". I also have sonarlint.nvim setup in my neovim setup.

After a bit of digging I found out that both sonarlint.nvim and nvim-jdtls are creating new jdtls servers which is the cause I feel. I'm not sure how to resolve it and looking for some help on this regards.

nvim-jdtls config:

local config = {
  cmd = { vim.fn.expand("~/.local/share/nvim/mason/bin/jdtls") },
  root_dir = vim.fs.dirname(vim.fs.find({ 'gradlew', '.git', 'mvnw' }, { upward = true })[1]),
}
require('jdtls').start_or_attach(config)

sonalint.nvim config:

local ft = {
  "javascript",
  "javascriptreact",
  'typescriptreact',
  'typescript',
  "java"
}
return {
  "https://gitlab.com/schrieveslaach/sonarlint.nvim.git",
  dependencies = {
    "williamboman/mason-lspconfig.nvim",
  },
  ft = ft,
  config = function()
    require("lspconfig")
    local analyzers = "~/.local/share/nvim/mason/share/sonarlint-analyzers/"
    require("sonarlint").setup({
      server = {
        cmd = {
          'sonarlint-language-server',
          '-stdio',
          '-analyzers',
          vim.fn.expand(analyzers .. "sonarjs.jar"),
          vim.fn.expand(analyzers .. "sonarjava.jar")
        },
      },
      filetypes = ft
    })
  end
}

Btw I'm using lazy as the package manages not sure if this helps.

Thanks in Advanced.

Thanks mfussenegger for the amazing work. Keep up the good work

[juhaku]

You might want to see my setup as it might help with you similar of "multiple LSP servers". The key is to have the correct root for all the servers. #613 (comment)

[allancomar]

I had similar issues before related to my configuration, meaning, I had a generic attach lsp for multiple languages that looked like:

            local mason_lspconfig = require('mason-lspconfig')
            local capabilities = vim.lsp.protocol.make_client_capabilities()
            capabilities = require('cmp_nvim_lsp').default_capabilities(capabilities)
            mason_lspconfig.setup_handlers({
                function(server_name)
                        require('lspconfig')[server_name].setup {
                            capabilities = capabilities,
                            on_attach = on_attach,
                            settings = servers[server_name],
                        }
                end,
            })

what happens is this code attached 1 lsp and the java file attached other. So I added the following:

            local mason_lspconfig = require('mason-lspconfig')
            local capabilities = vim.lsp.protocol.make_client_capabilities()
            capabilities = require('cmp_nvim_lsp').default_capabilities(capabilities)
            mason_lspconfig.setup_handlers({
                function(server_name)
                    if server_name ~= 'jdtls' then
                        require('lspconfig')[server_name].setup {
                            capabilities = capabilities,
                            on_attach = on_attach,
                            settings = servers[server_name],
                        }
                    end
                end,
            })

To my generic attach. not sure if there is better ways to avoid this but that solved for me.

[rogeriofrsouza]

Is jdtls started when you launch Neovim?
Could you try setting sonarlint.nvim as lazy?

local ft = {
  "javascript",
  "javascriptreact",
  'typescriptreact',
  'typescript',
  "java"
}
return {
  "https://gitlab.com/schrieveslaach/sonarlint.nvim.git",
  ft = ft,
  lazy = true,
  -- other settings
}