We’re using SonarLint 3.6.0.201806071228 (with Rational Application Developer 9.5.0.4 (believe this is the lastest version of SonarLint that works with this) and SonarQube 7.7.0.23042.
We’ve seen an issue where SonarQube is reporting :
For the record, the version of SonarJava on your server is 5.11.0.17289.
But I missed one important information from your first thread: if you are using connected mode, the rules configuration is not coming from SonarLint preferences (the screenshot you shown), but from the server quality profile.
Still the !unknownSymbol! in the rule message make me think something fishy is happening in the analyser. Maybe you could try to:
unbind your project t see if the same issue is reported by SonarLint in standalone mode
update SonarJava plugin on your server (latest version is 5.14.0.18788)