Java startup parameters: Difference between revisions

From Open-Xchange
(Created page with "The backend component is written in Java. The Java environment can be fine-tuned using several parameters which are explained here. Not every setting makes sense in every cont...")
 
No edit summary
 
Line 1: Line 1:
The backend component is written in Java. The Java environment can be fine-tuned using several parameters which are explained here. Not every setting makes sense in every context, though.
The backend component is written in Java. The Java environment can be fine-tuned using several parameters which are explained here. Not every setting makes sense in every context, though.


{| align="left" cellpadding="1" width="100%"
{| align="left" cellpadding="1" width="100%" class="wikitable sortable toptextcells"
|-
|-
!width="30%" align="left"| Parameter
!width="30%" align="left"| Parameter
Line 30: Line 30:
| Yes
| Yes
|
|
|-
| -Dosgi.compatibility.bootdelegation
| Yes
| Current value: '''false'''. After changing "-Dosgi.compatibility.bootdelegation" to true in SCR 1068 we had further internal discussions about the topic where a developer provided further previously not considered details about duplicate classes in the area of xml processing. These classes might lead to linkage errors at runtime due to multiple instances of the same class file being loaded. This further inside made as reconsider the the switch of compatibility.
|}
|}

Latest revision as of 16:05, 18 January 2013

The backend component is written in Java. The Java environment can be fine-tuned using several parameters which are explained here. Not every setting makes sense in every context, though.

Parameter currently in use Reasons for/against use
-XX:+UnlockExperimentalVMOptions No ...
-XX:+UseG1GC No ...
-XX:+UseConcMarkSweepGC Yes
-XX:+UseParNewGC Yes
-XX:CMSInitiatingOccupancyFraction=75 Yes
-XX:+UseCMSInitiatingOccupancyOnly Yes
-Dosgi.compatibility.bootdelegation Yes Current value: false. After changing "-Dosgi.compatibility.bootdelegation" to true in SCR 1068 we had further internal discussions about the topic where a developer provided further previously not considered details about duplicate classes in the area of xml processing. These classes might lead to linkage errors at runtime due to multiple instances of the same class file being loaded. This further inside made as reconsider the the switch of compatibility.