help with error running jdtls

[emilyyyylime]

Running jdtls outputs

OpenJDK 64-Bit server VM Warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release
WARNING: Using incubator modules: jdk.incubator.vector, jdk.incubator.foreign
An error has occured. See the log file
/path/to/log

Which according to someone else seems to indicate I'm using java < 17 but I deleted all files that have to do with java 11 and I'm still getting this.
I've tried asking in the Mattermost channel but it seems it's dead

[snjeza]

@Itay123TheKing could you attach your log (/path/to/log)?

[emilyyyylime]

@snjeza
log.txt

[snjeza]

@Itay123TheKing I can't reproduce the issue.
Could you show your running command?

[emilyyyylime]

@snjeza
Simply jdtls, but this ks just to test, in practice I want to integrate it with my text editor, in which the default configuration is also simply jdtls. Am I missing any arguments?

[rgrunber]

@Itay123TheKing can you try running :

/path/to/the/jdtls -data testWorkspace

I think I've seen similar errors if I don't specify it.

Update: #2191 (comment) , if this issue is the same, then now I'm a bit more sure this will be resolve once we fix that bug.

[emilyyyylime]

@rgrunber that in fact stops the An error has occurred message. But the warnings stay. what should I do to resolve them?

[emilyyyylime]

also does the workspace need to have any specific structure? I'm aware Java usually has some weird rules when it comes to folder names and file locations

[rgrunber]

I think the warnings are ok. As long as the language server remains up, it should be fine. If you check the path to the workspace you specified in to -data, there should be a file under /path/to/my/workspace/.metadata/.log The log file should contain something like :

!ENTRY org.eclipse.jdt.ls.core 1 0 2022-09-13 10:18:29.179
!MESSAGE class org.eclipse.jdt.ls.core.internal.JavaLanguageServerPlugin is started

!ENTRY org.eclipse.jdt.ls.core 1 0 2022-09-13 10:18:29.278
!MESSAGE Main thread is waiting

That would indicate the language server started up. You could also monitor this file for possible errors. The workspace is just where certain data and projects may be stored. It doesn't need any particular structure. The weird naming rules are more for projects.

[fbricon]

https://github.com/eclipse/eclipse.jdt.ls/blob/master/org.eclipse.jdt.ls.product/scripts/jdtls.py#L89 needs to be removed

[emilyyyylime]

@rgrunber now I'm glad I asked because I was under the impression the workspace had to be specifically my project directory, this makes it easier. thanks!

[emilyyyylime]

actually @rgrunber is it okay if I ask one more question?
In my editor I get on the very first character the warning: filename.java is a non-project file, only syntax errors are reported. I tried putting different depth paths in -data (and deleting the .metadata and jdt.ls-java-project every time I tried something new) and moving my file into a src directory - and even moving it inside the auto generated jdt.ls-java-project/src. How do I tell jdtls which files are project files?

[rgrunber]

actually @rgrunber is it okay if I ask one more question? In my editor I get on the very first character the warning: filename.java is a non-project file, only syntax errors are reported. I tried putting different depth paths in -data (and deleting the .metadata and jdt.ls-java-project every time I tried something new) and moving my file into a src directory - and even moving it inside the auto generated jdt.ls-java-project/src. How do I tell jdtls which files are project files?

Are you placing your filename.java inside the workspace? I'm not sure if that would work, and I'd recommend against doing that. The location you pass to -data (the "workspace" location) is not meant to be used by users to place their projects. It is more of a location where the language server stores certain state-based information. You should be able to open any other folder location or file and have it working in JDT-LS.

[emilyyyylime]

@rgrunber ohh I totally misunderstood earlier - it's called a workspace but it's not a space to be worked in :P.
Do you know why I'm getting the aforementioned warning though?

[rgrunber]

If the source file is placed within jdt.ls-java-project that might trigger it. That location is meant to be left alone.

The code that's probably being triggered is https://github.com/eclipse/eclipse.jdt.ls/blob/e7235f90d6a1e85aa22c7621858a54529b811188/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/DiagnosticsHandler.java#L48

Does the problem go away if you clear out the workspace and open a project/file from some other location ?

[emilyyyylime]

@rgrunber (sorry for the late reply)
No, I made sure to move the java file out of there. If I understood you correctly I tried rm -rfing the jdtls-wrokspace directory and then opening my file with my text editor, and the problem still was like that
my folder structure looks like this:

(...)/projectname/file.java
(...)/jdtls-workspace/...

is this correct?

[rgrunber]

Actually, I think this is expected. I see it as well.

[Trace - 12:41:36 p.m.] Sending request 'textDocument/codeAction - (29)'.
Params: {
    "textDocument": {
        "uri": "file:///tmp/foo/Test.java"
    },
    "range": {
        "start": {
            "line": 0,
            "character": 0
        },
        "end": {
            "line": 0,
            "character": 1
        }
    },
    "context": {
        "diagnostics": [
            {
                "range": {
                    "start": {
                        "line": 0,
                        "character": 0
                    },
                    "end": {
                        "line": 0,
                        "character": 1
                    }
                },
                "message": "Test.java is a non-project file, only syntax errors are reported",
                "code": "16",
                "severity": 2,
                "source": "Java"
            }
        ],
        "only": [
            "quickfix"
        ]
    }
}

However, there are some quick-fixes for it offered by the language server :

[Trace - 12:41:36 p.m.] Received response 'textDocument/codeAction - (29)' in 9ms.
Result: [
    {
        "title": "Report compilation errors for this file",
        "kind": "quickfix",
        "diagnostics": [],
        "command": {
            "title": "Report compilation errors for this file",
            "command": "java.project.refreshDiagnostics",
            "arguments": [
                "file:///tmp/foo/Test.java",
                "thisFile",
                false
            ]
        }
    },
    {
        "title": "Report compilation errors for any non-project file in the current session",
        "kind": "quickfix",
        "diagnostics": [],
        "command": {
            "title": "Report compilation errors for any non-project file in the current session",
            "command": "java.project.refreshDiagnostics",
            "arguments": [
                "file:///tmp/foo/Test.java",
                "anyNonProjectFile",
                false
            ]
        }
    }
]

You could try opening a folder containing Java files (rather than just a standalone file), and see if it behaves differently. However the language server is up and working even in the standalone case.