Windows command line service.bat installer doesn't set the LIMIT_BUFFER tomcat parameter correctly

When JIRA is installed as a service from the command line in service.bat (service.bat install JIRA) the -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true parameter is invoked to stop a memory leak in Tomcat caching JSPs.

The line is executed as

"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Djava.io.tmpdir=%CATALINA_BASE%\temp;-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties" --JvmMs 128 --JvmMx 512 --Startup auto || call "%~dp0\permgenservice.bat"

when there should be a ; delimiter between -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Djava.io.tmpdir=%CATALINA_BASE%\temp;

It should be

"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true;-Djava.io.tmpdir=%CATALINA_BASE%\temp;
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties" --JvmMs 128 --JvmMx 512 --Startup auto || call "%~dp0\permgenservice.bat"

The workaround for existing installs is to modify the entry directly in the windows registry.