[midPoint] Certain application.yml settings not working in 3.9

[Stacy Brock]

Hello,

We are seeing some odd behavior on a clean install of midPoint 3.9 
related to certain settings not working properly when set in 
$MIDPOINT_HOME/application.yml

We have the following application.yml on our midPoint 3.8 instance and 
it is working as expected:

server:
   address: 127.0.0.1
   port: 8080
   session:
     timeout: 60
   use-forward-headers: true
   tomcat:
     port-header: X-Forwarded-Port
     protocol-header: X-Forwarded-Proto
     protocol-header-https-value: https
     internal-proxies: 127.0.0.1
     basedir: /opt/midpoint/var/tomcat
     accesslog:
       enabled: true
       request-attributes-enabled: true
       directory: log
       prefix: tomcat_access_log
       suffix: .log
       buffered: false

When the same application.yml is used in midPoint 3.9, none of the the 
tomcat-related settings seem to work. For example, the Tomcat working 
dir shows up in /tmp despite being set to /opt/midpoint/var/tomcat 
directly, and there is no access log to be found.

[root at midpoint-vd01 var]# cd /tmp
[root at midpoint-vd01 tmp]# ls -la
total 80
drwxrwxrwt. 42 root     root      4096 Nov 15 03:35 .
dr-xr-xr-x. 18 root     root      4096 Nov 13 14:40 ..
drwxr-xr-x   3 midpoint midpoint    37 Nov 14 13:07 bundle-981357110
... trimmed for brevity ...
drwxr-xr-x   3 midpoint midpoint    17 Nov 13 16:17 
tomcat.5896799556798523255.8080
drwxr-xr-x   3 midpoint midpoint    17 Nov 13 16:34 
tomcat.7393188119975923073.8080
drwxr-xr-x   3 midpoint midpoint    17 Nov 14 11:08 
tomcat.7504718818560878961.8080
drwxr-xr-x   3 midpoint midpoint    17 Nov 14 12:13 
tomcat.7557699004309110545.8080
drwxr-xr-x   3 midpoint midpoint    17 Nov 14 12:26 
tomcat.7791693371928358167.8080
drwxr-xr-x   3 midpoint midpoint    17 Nov 14 12:41 
tomcat.8654292536453675004.8088
drwxr-xr-x   3 midpoint midpoint    17 Nov 14 12:43 
tomcat.8835936531569122577.8080

What's very odd is that if we change the server.port to something else, 
8088 for example, that DOES work.

Has anyone else seen this behavior in 3.9?

Thanks,
-Stacy

-- 
Stacy Brock, Software Engineer, IT Infrastructure
Oregon State University | University Information and Technology