Hide Forgot
Description of problem: There are incorrect system properties in standalone-osgi.xml after installing while using "Disable OptaPlannerExecution Server" option. Version-Release number of selected component (if applicable): 6.3.0.ER2 How reproducible: always Steps to Reproduce: 1. Run Installer 2. Tick "Disable OptaPlannerExecution Server" in Advanced config tab 3. Finish Actual results: System properties elemnt in osgi xml file looks like this: <system-properties> <property name="org.kie.example" value="true"/> <property name="org.jbpm.designer.perspective" value="full"/> <property name="designerdataobjects" value="false"/> </system-properties> As you can see there are 2 properties missing. One is specific to "Disable OptaPlannerExecution Server" option, while the other is regarding "org.kie.server.repo" and I am not quite sure if this should be here too. Expected results: Standalone-osgi.xml system properties element should contain same items that other configuration files do. <system-properties> <property name="org.kie.server.repo" value="${jboss.server.data.dir}"/> <property name="org.optaplanner.server.ext.disabled" value="true"/> <property name="org.kie.example" value="true"/> <property name="org.jbpm.designer.perspective" value="full"/> <property name="designerdataobjects" value="false"/> </system-properties> Additional info:
Hi Dominik, I've adjusted the installer to modify standalone-osgi.xml to be modified in an identical way to the other standalone-*.xmls.
Hi Tom, thanks for the fix. Tests now fails on domain configuration. What about domain.xml and host.xml? I have noticed that they include <system-properties> too and this option should therefore be there aswell. Could you please confirm? If that is true, this needs more fixing, since domain.xml and host.xml servers should also have the option (disabled=true). Let me know as soon as possible. Thanks! Dominik
Looks like this need to be fixed in domain.xml too. Not sure about host.xml, but I think they use properties sepcified in domain.xml so i think it should be untouched. Moving back to ASSIGNED so the property is included in "domain.xml" too.
I have noticed that fix for BPMS is already in rebuilt ER3. Occurs only in BRMS now.
BRMS has had the fix applied as well.
Verified in 6.3.0.CR2.