jvm_opts does not get overwritten

Question

jvm_opts does not get overwritten

Closed this issue 4 years ago · 3 comments

mbloch1986 commented 5 years ago

The value defined in jvm_opts does not overwrite the value in the start-env file, if the start-env file in the snapshot already contains a value for jvm_opts.

We should make sure that the value defined in jvm_opts always overwrites the value in the start-env since we explicit set it here.

Answer 1 · 2019-10-16T06:13:20.000Z

I think one way to get around this is to add custom hooks and always overwrite the value after the custom hook.

Answer 2 · 2020-04-25T06:59:33.000Z

#193 is about using aem::config to reset the AEM start binaries. If we use this in our default provisioning process the value for jvm_opts get's always injected into the start binaries before AEM starts. Therefore if we solve #193 we are solving this problem as well.

Answer 3 · 2020-05-12T06:45:39.000Z

Changes are included in puppet-aem-curator version 3.12.0. We are now always resetting the AEM binaries.