-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java Plugin not Being Started #14944
Comments
I can reproduce this problem with cpptools plugin as well Logs from the plugin's container
this problem is reproducible time to time |
Reproducible with php language remote plugin, I think pretty critical for code-ready |
Logs after first starting workspace and opening a maven projectStarting the deployer with the list of resolvers [ LocalDirectoryPluginDeployerResolver {}, GithubPluginDeployerResolver { unpackedFolder: '/tmp/github-remote' }, HttpPluginDeployerResolver { unpackedFolder: '/tmp/http-remote' }, VsCodePluginDeployerResolver { vscodeExtensionsFolder: '/tmp/vscode-extension-marketplace' } ] Theia Endpoint 19/pid listening on port 2503 Found the list of default plugins ID on env: undefined Found the list of plugins ID on env: local-dir:///plugins/sidecars/redhat_java_latest Found the list of default plugins ID from CLI: undefined unzipping the VS Code extension 'redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix' to directory: /tmp/vscode-unpacked/redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix unzipping the VS Code extension 'redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix' to directory: /tmp/vscode-unpacked/redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix PluginTheiaDirectoryHandler: accepting plugin with path /tmp/vscode-unpacked/redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix Resolving "redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix" as a VS Code extension... Resolved "redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix" to a VS Code extension "java@0.50.0" with engines: { vscode: '^1.36.0' } PluginTheiaDirectoryHandler: accepting plugin with path /tmp/vscode-unpacked/redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix Resolving "redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix" as a VS Code extension... Resolved "redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix" to a VS Code extension "vscode-java-debug@0.20.0" with engines: { vscode: '^1.32.0' } the accepted plugins are [] the acceptedFrontendPlugins plugins are [] the acceptedBackendPlugins plugins are [ PluginDeployerEntryImpl { originId: 'local-dir:///plugins/sidecars/redhat_java_latest', pluginId: 'redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix', map: Map { 'package.json' => [Object] }, changes: [ 'PluginVsCodeFileHandler', 'PluginVsCodeDirectoryHandler' ], acceptedTypes: [ 1 ], currentPath: '/tmp/vscode-unpacked/redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix/extension', initPath: '/plugins/sidecars/redhat_java_latest/redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix', resolved: true, resolvedByName: 'LocalDirectoryPluginDeployerResolver' }, PluginDeployerEntryImpl { originId: 'local-dir:///plugins/sidecars/redhat_java_latest', pluginId: 'redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix', map: Map { 'package.json' => [Object] }, changes: [ 'PluginVsCodeFileHandler', 'PluginVsCodeDirectoryHandler' ], acceptedTypes: [ 1 ], currentPath: '/tmp/vscode-unpacked/redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix/extension', initPath: '/plugins/sidecars/redhat_java_latest/redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix', resolved: true, resolvedByName: 'LocalDirectoryPluginDeployerResolver' } ] local path to deploy on remote instance [ '/tmp/vscode-unpacked/redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix/extension', '/tmp/vscode-unpacked/redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix/extension' ] Deploying backend plugin "java@0.50.0" from "/tmp/vscode-unpacked/redhat.java.latest.wqwczbcine.java-0.50.0-1825.vsix/extension/dist/extension" Deploying backend plugin "vscode-java-debug@0.20.0" from "/tmp/vscode-unpacked/redhat.java.latest.xqqajxsbmd.vscode-java-debug-0.20.0.vsix/extension/dist/extension" After refreshing a browser LS is launched |
It seems that plugin activation is not happening in this case. Couple of datapoints:
|
Changed title: Java commands are not registered, which indicates that the vscode-java extensions is never started. Also: plugin activation are not visible in the browser log. |
I am having trouble reproducing now. However, one thing I noticed is that in the plugin host image output, the line
Was missing when the initialization failed. The log comes from plugin-host-rpc.ts#135, and indirectly from PluginManagerExtImpl#$start(), which is in plugin-manager.ts#155. |
Further info: the $start message seems to be sent to the remote plugin manager, but I don't see the init message that should be displayed if $start is indeed executed in the plugin host. |
The error has been fixed by PR eclipse-che/che-theia#508 |
It has been reproduced in Eclipse Che 7.11.0-SNAPSHOT:
Refreshing of browser doesn't work in most cases. |
could you provide logs from java-plugin container? |
@svor, @benoitf: here java plugin container logs are:
|
@svor: issue has been reproduced both with TLS enabled and disabled. |
@svor: this time the issue has been introduced by changes in PR eclipse-che/che-theia#676 |
this issue is not about Java LS. The problem is about plugin-remote-endpoint . If execute
|
Describe the bug
Java LS server didn't start from the first time of workspace loading and required refreshing of browser's tab:
https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che-regular-tests/view/K8S/job/Single-Che-master-check-E2E-Happy-path-tests-against-k8s/2581/ :
Workaround
Refreshing browser's tab restores LS server initialization https://github.com/eclipse/che/blob/master/e2e/pageobjects/ide/Ide.ts#L220-L226.
Screencast
https://youtu.be/KBL5ug1idEI
Screenshot
Related issue
#14283
Che version
Logs and configs
https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che-regular-tests/view/K8S/job/Single-Che-master-check-E2E-Happy-path-tests-against-k8s/2581/artifact/logs-and-configs/
Che version
Steps to reproduce
https://github.com/eclipse/che/blob/master/e2e/tests/e2e_happy_path/HappyPath.spec.ts
Devfile
https://github.com/eclipse/che/blob/master/e2e/files/happy-path/happy-path-workspace.yaml
Runtime
kubectl version
)oc version
)minishift version
andoc version
)docker version
andkubectl version
)Installation method
Environment
The text was updated successfully, but these errors were encountered: