Details
Description
Current behaviour on Linux :
$ ./sonar.sh start Starting sonar... Started sonar. $ ./sonar.sh start Starting sonar... sonar is already running.
i.e. only one running instance.
And current behaviour on Windows :
> StartSonar.bat Launching a JVM... > StartSonar.bat Launching a JVM...
i.e. several running instances - for example it's possible to start one instance using service and another one from console.
Thus we have an inconsistency in behaviour under different OSs. And moreover in case of Windows this behaviour is misleading and error-prone.
So IMO would be better to disallow multiple instances on Windows. In order to do this following options should be added to wrapper.conf ( http://wrapper.tanukisoftware.com/doc/english/prop-single-invocation.html ) :
wrapper.single_invocation=true
With this option enabled, attempt to start second instance will lead to a following message :
wrapper | ERROR: Another instance of the Sonar application is already running.
Issue Links
- is related to
-
SONAR-3964
Default value of 'wrapper.single_invocation' in 'wrapper.conf' should be 'false'
-
Done in 356ce27.