Warning when trying to open Java LS Log file #13428
Labels
kind/bug
Outline of a bug - must adhere to the bug report template.
Milestone
Comments
l0rd
added
kind/bug
|
@l0rd did the java language server actually start? If jdt.ls is not started, there won't be a log file and the message is to be expected. |
|
@tsmaeder it looks like the language server is started: $ k exec -ti workspace1bszgp7t1ogdm5xu.workspace-5b9c6df86-ksfnn -c ghs sh
$ /projects $ ps -ef | grep java
root 43 19 3 22:27 ? 00:00:33 /usr/lib/jvm/default-jvm/bin/java --add-modules=ALL-SYSTEM --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED -Declipse.application=org.eclipse.jdt.ls.core.id1 -Dosgi.bundles.defaultStartLevel=4 -Declipse.product=org.eclipse.jdt.ls.core.product -Dfile.encoding=UTF-8 -noverify -Xmx1G -XX:+UseG1GC -XX:+UseStringDeduplication -jar /tmp/vscode-unpacked/redhat.java.latest.vjpvzgzlbh.java-0.45.0-1523.vsix/extension/server/plugins/org.eclipse.equinox.launcher_1.5.400.v20190514-1658.jar -configuration /tmp/vscode-unpacked/redhat.java.latest.vjpvzgzlbh.java-0.45.0-1523.vsix/extension/server/config_linux -data /home/theia/.theia/workspace-storage/be0a81bfde25dc291c35808bdaf5f836/redhat.java/jdt_wsAnd I have eventually found the log as well: |
|
UPDATE I have fixed the problem with the container OOMKilled (not enough memory for the yaml LS) but I still have the Java LS log file error. $ k describe pod workspace1bszgp7t1ogdm5xu.workspace-5b9c6df86-ksfnn
(...)
2au:
Container ID: docker://fd8d5eb50aa2bfa8330c5d32df6a334ce3c9c0267d69bb9c4988f72fcd19122d
Image: eclipse/che-theia-endpoint-runtime:next
Image ID: docker-pullable://eclipse/che-theia-endpoint-runtime@sha256:74885ed9f5ea6b6b11866ab2c3e834841a4e89d07d895cc7651e16b724c94f5f
Port: <none>
Host Port: <none>
State: Running
Started: Wed, 12 Jun 2019 00:28:04 +0200
Last State: Terminated
Reason: OOMKilled
Exit Code: 137
Started: Wed, 12 Jun 2019 00:27:41 +0200
Finished: Wed, 12 Jun 2019 00:27:47 +0200
Ready: True
Restart Count: 2
Limits:
memory: 134217728
Requests:
memory: 134217728
Environment:
THEIA_PLUGINS: local-dir:///plugins/sidecars/redhat_vscode_yaml_latest
CHE_WSAGENT_CORS_ALLOW__CREDENTIALS: true
CHE_MACHINE_TOKEN:
CHE_WORKSPACE_WSAGENT__JAVA__OPTIONS: -XX:MaxRAM=600m -XX:MaxRAMFraction=1 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xms50m -Dfile.encoding=UTF8 -Djava.security.egd=file:/dev/./urandom
JAVA_OPTS: -XX:MaxRAM=150m -XX:MaxRAMFraction=2 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xms20m -Djava.security.egd=file:/dev/./urandom
CHE_PROJECTS_ROOT: /projects
CHE_API: http://che-che.192.168.99.100.nip.io/api
MAVEN_OPTS: -XX:MaxRAM=150m -XX:MaxRAMFraction=2 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xms20m -Djava.security.egd=file:/dev/./urandom
CHE_WORKSPACE_NAME: petclinic-dev-environment
CHE_WORKSPACE_LOGS_ROOT__DIR: /workspace_logs
CHE_WSAGENT_CORS_ENABLED: true
CHE_WORKSPACE_NAMESPACE: che
CHE_MACHINE_NAME: 2au
CHE_API_INTERNAL: http://che-che.192.168.99.100.nip.io/api
CHE_WORKSPACE_ID: workspace1bszgp7t1ogdm5xu
CHE_API_EXTERNAL: http://che-che.192.168.99.100.nip.io/api
CHE_AUTH_ENABLED: false
Mounts:
/plugins from claim-che-workspace (rw)
/projects from claim-che-workspace (rw)
/var/run/secrets/kubernetes.io/serviceaccount from che-workspace-token-c6nck (ro)
/workspace_logs from claim-che-workspace (rw)
(...)And this is the container log $ kubectl logs workspace1bszgp7t1ogdm5xu.workspace-5b9c6df86-ksfnn -c 2au
Starting 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 18/pid listening on port 2505
Found the list of default plugins ID on env: undefined
Found the list of plugins ID on env: local-dir:///plugins/sidecars/redhat_vscode_yaml_latest
Found the list of default plugins ID from CLI: undefined
unzipping the plugin ProxyPluginDeployerEntry {
deployer:
PluginVsCodeFileHandler { unpackedFolder: '/tmp/vscode-unpacked' },
delegate:
PluginDeployerEntryImpl {
originId: 'local-dir:///plugins/sidecars/redhat_vscode_yaml_latest',
pluginId:
'redhat.vscode-yaml.latest.ezywmsemkz.redhat.vscode-yaml-0.4.0.vsix',
map: Map {},
changes: [],
acceptedTypes: [],
currentPath:
'/plugins/sidecars/redhat_vscode_yaml_latest/redhat.vscode-yaml.latest.ezywmsemkz.redhat.vscode-yaml-0.4.0.vsix',
initPath:
'/plugins/sidecars/redhat_vscode_yaml_latest/redhat.vscode-yaml.latest.ezywmsemkz.redhat.vscode-yaml-0.4.0.vsix',
resolved: true,
resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
deployerName: 'PluginVsCodeFileHandler' }
(node:18) UnhandledPromiseRejectionWarning: Error: ENOMEM: not enough memory, write
(node:18) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:18) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. |
|
This works now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When trying to open the Java Language Server Log file from the command palette:
the log file is not opened and the following warning is shown:
Reproduction Steps
Start a workspace using this devfile:
Open the command palette and open the Java Log File
OS and version:
macOS / minikube / nightly che-server / chectl / helm / jtd ls 0.45.0
The text was updated successfully, but these errors were encountered: