Hi, it’s going to be hard to help you without the error message. Just to double-check, you are not running the Community Edition and Enterprise Edition on the same machine, right?
Just make sure you don’t have any TCP port conflict It does not look like it’s the issue here.
I don’t know much about this plugin, so I’m not sure that I’m able to help. Maybe someone else will answer on this specific error. I have a question though: Are you sure you need this community plugin, given the fact that you benefit from the built-in CFamily analyzer in Enterprise Edition?
Just make sure you don’t have any TCP port conflict
Answer from our IT: The two server instances are running on two different physical machines. It’s for sure not an IP problem. We can also turn off the Community server and the problem is the same on the Enterprise server.
I don’t know much about this plugin …
The general question/issue has nothing to do with the plugin.
The question is, what is the Enterprise server doing if there is an ERROR in the LOG file?
… and why is the behaviour different compared to the Community server?
Original question was: Is there an option to define/configure the behaviour?
The same thing as the Community Edition. SonarQube Behaviours are not tights to a log level: and error during startup often mean that SonarQube won’t start, while an error during normal operation only means something failed, but SonarQube can still operate.
The resolution of your problem will most likely be linked to what change in Enterprise Edition, mostly the additional built-in analyzers in that case (maybe a conflict on rule key for example).
Do you have any more information in the stack trace below the error?