As a Security Server Admin I want that xroad-jetty process is not consuming redundant memory so that Security Server resources are not wasted

Affected components: xroad-jetty Affected documentation: - Estimated delivery: Q4/2017 External reference: https://jira.csc.fi/browse/PVAYLADEV-978

Problem When fixing the issue https://github.com/vrk-kpa/xroad-joint-development/issues/146 it was later noticed that the usage of Security Server memory was increased. To looking at this memory related problem more closely, it was found out that due to Logback bugfix was taken into use, xroad-jetty process now starts using two process (normally only one process should be started). And the additional process is not inheriting memory settings as it should be but instead it is getting default amount of heap memory (default is 1/4).

Based on preliminary study, it is proposed that Jetty's logging-logback.mod module needs to be modified so that [exec]-part is removed and its shell parameter should be set as a starting parameter of Jetty (xroad-jetty.conf).

Acceptance criteria

xroad-jetty process is not starting additional process and is not consuming redundant memory
UI automation tests are passed successfully

vrk-kpa / xroad-joint-development

As a Security Server Admin I want that xroad-jetty process is not consuming redundant memory so that Security Server resources are not wasted #185