LMP 3.10 and 3.10.1 do not pickup the change from server.xml

[gkwan-ibm]

LMP 3.10 and 3.10.1 do not pickup the change from server.xml. Tried on Mac. LMP 3.9 has no problem.

Steps to reproduce the problem.

• start jaeger from this doc
• git clone https://github.com/openliberty/guide-microprofile-telemetry-jaeger.git
• cd guide-microprofile-telemetry-jaeger/start/system
• mvn liberty:dev
• cd guide-microprofile-telemetry-jaeger/start

• replace system/src/main/liberty/config/server.xml by the following. It only added <feature>mpTelemetry-1.1</feature>

  
  <server description="system service">
  
  <featureManager>
      <feature>cdi-4.0</feature>
      <feature>jsonb-3.0</feature>
      <feature>jsonp-2.1</feature>
      <feature>restfulWS-3.1</feature>
      <feature>mpTelemetry-1.1</feature>
  </featureManager>
  
  <httpEndpoint httpPort="${http.port}"
                httpsPort="${https.port}"
                id="defaultHttpEndpoint" host="*" />
  
  <webApplication location="guide-microprofile-telemetry-system.war"
                  contextRoot="/" />

- create `system/src/main/resources/META-INF/microprofile-config.properties`

otel.service.name=system otel.sdk.disabled=false

- visit http://localhost:9080/system/properties
- visit http://localhost:16686/
  - You can view the traces for the system service under the Search tab. Select the `system` service in the *Select A Service* menu and click the *Find Traces* button at the end of the section. You’ll see the result as following but not:

![Screenshot 2024-03-12 at 11 34 39 AM](https://github.com/OpenLiberty/ci.maven/assets/29576299/0a086658-eb64-45c0-bd30-6a0d162743a1)

[gkwan-ibm]

workaround: press r in the dev mode console to force restarting the Liberty instance

[cherylking]

I just verified changes to server.xml are picked up by dev mode in version 3.10.1 using another getting started guide.

[scottkurz]

@gkwan-ibm - Not sure if you are saying that the install feature (of the new mp telemetry feature) seems to be happening but it's still not working vs. the feature isn't getting installed at all.

It'd probably help to run with mvn -X logging. Just be sure to redirect it somewhere outside of the original filesystem (e.g. up a level like mvn liberty:-dev -X > ../trace.log so dev mode doesn't react to the log file updates.

[gkwan-ibm]

close

• I closed all my consoles, retried the guide with new consoles, and could not reproduce the problem