Socket GLSP Node server closing connection

[gee4vee]

I am trying to get the workflow example running in our VS Code extension as a baseline for a new visual editor we will work on. I have gotten all the client and node server code copied and compiled. However, it just hangs at the line await serverProcess.start(); during extension activation. How can I debug this further?

I am using v2.3.0 of the GLSP components.

[gee4vee]

I can now see that the GLSP server starts briefly and then terminates.

GLSP-Server: Debugger listening on ws://127.0.0.1:59020/7a9f2138-8e99-448c-9d33-eb663d751e2b
For help, see: https://nodejs.org/en/docs/inspector

extensionHostProcess.js:163
GLSP-Server: Debugger attached.

extensionHostProcess.js:163
GLSP-Server: Waiting for the debugger to disconnect...

Is there a way I can dig into this to see why?

[martin-fleck-at]

Hi @gee4vee, with what arguments do you start the server process? In the tasklist example we use the following creation:

        serverProcess = new GlspSocketServerLauncher({
            executable: modulePath,
            socketConnectionOptions: { port: JSON.parse(process.env.TASKLIST_SERVER_PORT || DEFAULT_SERVER_PORT) },
            additionalArgs: ['--no-consoleLog', '--fileLog', '--logDir', LOG_DIR],
            logging: true
        });

https://github.com/eclipse-glsp/glsp-examples/blob/master/project-templates/node-json-vscode/tasklist-vscode/extension/src/tasklist-extension.ts#L39-L44

As you can see, logs are written to a directory. If you want the logs directly in the Debug Console view after starting from the launch configuration in VS Code, you need to remove the '--no-consoleLog' argument. Typically you should these entries first:

GLSP-Server: 2:44:15 PM info -  [SocketServerLauncher] The GLSP server is ready to accept new client requests on port: 33665 
[GLSP-Server]:Startup completed. Accepting requests on port:33665

extensionHostProcess.js:163
GLSP-Server: 2:44:15 PM info -  [SocketServerLauncher] Starting GLSP server connection 
2:44:16 PM info -  [DefaultGLSPServer] Initializing server with: applicationId: 27c714e5-005f-4bcf-bda0-be491e880c68, protocolVersion: 1.0.0 

If the process fails before that, I'd definitely try to wrap the start call into a try-catch, e.g.:

try {
   await serverProcess.start();
} catch(error) {
  // log and check error
}

With that, do you see any additional errors?