Question regarding --J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS system property

[Jakov Varenina]

Hi devs,

When the --J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS system property is 
set, the server/locator ignores the log level specified in the custom 
Log4J configuration file at the startup. Is this expected behavior?


I could only find one note related to the above property in the "change 
loglevel" command document 
https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html 
:


"When using a custom Log4J configuration, this command takes effect only 
if the member whose logging level you want to change was started using 
the --J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS system property."


From this note, it is not clear what other effects of this system 
property are besides allowing this command to execute. I observed in 
tests that the geode log-level parameter (e.g., start server 
--log-level=debug) and custom Log4J log-level parameter (e.g., name="org.apache.geode" level="DEBUG">) are mutually exclusive. Users 
can choose between these two options with the LOG_LEVEL_UPDATE_OCCURS 
system property. Is this a correct understanding?


Best Regards,
Jakov

Windows pipelines for geode-native seems to be failing

[Mario Salazar de Torres]

Hi everyone,

It seems that both Windows pipelines for geode-native are failing, each of them 
for a different version. Here are some failed executions:

  *   Windows 2016/2017 pipeline:
 *   
https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-windows-2016-vs-2017-debug/builds/273
 *   
https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-windows-2016-vs-2017-debug/builds/272
  *   Windows 2019 pipeline:
 *   
https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-windows-2019-vs-2019-debug/builds/267
 *   
https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-windows-2019-vs-2019-debug/builds/268

As it sems the issue with Windows 2016/2017 pipeline seems to be related to 
OpenSSL, given that as you can see here: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-windows-2016-vs-2017-debug/builds/267#L626a0857:62
 whenever it was working, OpenSSL 1.1.1n instead of the version currently used 
(1.1.1i as can be seen here: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-windows-2016-vs-2017-debug/builds/272#L62838563:52)
I am not sure why the version of OpenSSL changed, and at least, it seems that 
there is no specific change for it in the repository. Have packer image changed 
recently?

And as for the case of Windows 2019 pipelines seems to be related to some 
GCP/infrastructure issues :S


So, I was wondering if anyone with the right permissions could look at it?

BR,
Mario.