use of init container can break brokerProperties system property set via JAVA_OPTS in profile, using JDK_JAVA_OPTIONS would just fix that

[gtully]

If an init container replaces the artemis.profile, any modification via JAVA_OPTS are lost, leading to a loss of the operator supplied system property and missing properties.

 message: 'Status out of sync - missing status entry for keys: [broker.properties]'
 reason: OutOfSync
 status: Unknown
 type: BrokerPropertiesApplied```

Using JDK_JAVA_OPTIONS env var to directly configure the jvm will avoid this problem of inter-dependence on the run scripts etc.
 

[brusdev]

The fix will be included in 1.0.16

[gtully]

Note: the jvm outputs to stderr that the env var is in use. That is a little too verbose for our use case, but I think being independent of the run scripts is advantageous.
see: https://docs.oracle.com/en/java/javase/11/tools/java.html#GUID-3B1CE181-CD30-4178-9602-230B800D4FAE__USINGTHEJDK_JAVA_OPTIONSLAUNCHERENV-F3C0E3BA:~:text=.%20When%20JDK_JAVA_OPTIONS%20is%20set%2C%20the%20launcher%20prints%20a%20message%20to%20stderr%20as%20a%20reminder.