Add more tips to Troubleshooting doc (#98)

* Add more tips to Troubleshooting doc

Signed-off-by: Michael Vorburger <[email protected]>

* Add reminder re. Terminal Tabs to Troubleshooting doc

* Update troubleshoot.md

* Update troubleshoot.md

* Update docs/troubleshoot.md

Signed-off-by: Gunnar Wagenknecht <[email protected]>

---------

Signed-off-by: Michael Vorburger <[email protected]>
Signed-off-by: Gunnar Wagenknecht <[email protected]>
Co-authored-by: Gunnar Wagenknecht <[email protected]>

Author: vorburger

docs/troubleshoot.md

@@ -49,6 +49,8 @@ see [issue #94](https://github.com/salesforce/bazel-vscode-java/issues/94).
 1. Run the _Java: Synchronize Projects with Bazel Project View_ command
 1. Run the _Java: Refresh Classpath from Bazel BUILD file_ command
 
+You could also try to uninstall and reinstall the extension, to see if that helps.
+
 ## Logs
 
 Check out the following places for log-like details to spot any problems:
@@ -63,6 +65,16 @@ Please attach (or copy/paste) all x3 if you file issues for support.
 (Rename `.log` to e.g. `log.txt` and `client.log.YYYY-MM-DD` to e.g. `client.log.YYYY-MM-DD.json`
 in order to be able to upload as attachment to GitHub issues.)
 
+The Bazel and JDT Job status is not in these log files, but visible
+on the _Terminal_ view _Bazel Build Status_ and _Java Build Status_ tabs;
+if in doubt, have a look at that as well (see also [issue #100](https://github.com/salesforce/bazel-vscode-java/issues/100)).
+
+There is a known limitation during initialization of the Java Language Server.
+While the initialization is ongoing the _Bazel Build Status_ will remain empty.
+It only starts working _after_ initialization completed.
+To work around this limitation you should configure a _static_ port for the extension to use.
+This can be done by adding `-Djava.bazel.staticProcessStreamSocket=22222` to `"java.jdt.ls.vmargs":` option in `.vscode/settings.json`.
+
 ## Extensions
 
 Please note that this _Bazel for Java_ extension (`sfdc.bazel-vscode-java`, which adds support for Bazel's **Java** rules to VSC), is technically completely independent of _[the VSC Bazel](https://marketplace.visualstudio.com/items?itemName=BazelBuild.vscode-bazel)_ extension (`BazelBuild.vscode-bazel`, which adds generic support for Bazel `BUILD` files editing, and "externally running" any Bazel targets; but specific nothing for Java).