In 16.3.2, the JVM parameters for backgroundServer are not used, jvmParameters for jobSchedulerInstance have to be used

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Starting 16.3.2, with an additional server type “bg” added to the possible instances for backgroundServer. Previously the jvmParameters setting would apply to BG only as single service type. Now with the addition of report service, the setting is still there but not in use

STEPS TO REPRODUCE:

1. Install a vanilla 16.3.2 or upgrade to 16.3.2
2. Open the properties.xml
3. Go to the line for backgroundServer – notice the jvmParameters setting.
4. Now note you also have two jobSchedulerInstance entries:
   • <jobSchedulerInstance id="bg"
   • <jobSchedulerInstance id="report"
   • Both have their own JVM configuration.
5. Deploy and start bg and report services
6. Check the memory used by the service/pid or check servicebgcmd.conf and servicereportcmd.conf

Expected Results: Comparing to app – there is no global JVM setting on applicationServer and only applicationServerInstance JVM config is used. So bg should likely not have JVM parameters attribute on backgroundServer node. 

Actual Results: backgroundServer has JVM parameters which still has the old setting after upgrade, however this setting is not in use. Only jvmParameters specific to jobSchedulerInstance are taken into account.

Environment

Clarity 16.3.2+

Resolution

Workaround:

1. Manually update the jvmParameters in the properties for both jobSchedulerInstance nodes,
2. Redeploy services.
3. Ignore the setting information on backgroundServer line.

Reviewed as DE170878, Working as Designed:

• We have provided JVMs for both BG and Report service instances to give customers to have control on both the service based on his consumption.
• For instance, a customer with heavy BG service usage and lighter report service usage can allocate a higher JVM to BG and a more moderate JVM to the report service, or vice-versa.
• You can deploy Report and BG service without defining JVM parameters on instance level
• If you don't specify JVM, Both BG and Report service will take JVM from Background service and will have the same amount each (i.e. 4GB).