-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.14.1
-
None
What are the steps to reproduce your problem?
To test the issue, just execute 9199.zip
and use the pom.xml to switch between 7.14.1-ee (non-working) and 7.12.4.-ee (working).
What is the problem?
The issue is that the customer has changed the loggingContextActivityId property from it's default value:
loggingContextActivityId: activityName
In their original version 7.12.4, this works as expected, as seen in these log messages (note that the activityName <key, value> pair exists in the before and after repository service API use messages:
After changing the pom.xml to use 7.14.x-ee, you can see that the activityName exists in before log message but it is gone from the after log message:
What would be the expected behavior:
The activityName should exist in the MDC before and after using Camunda APIs.
Hints (optional):
The customer has provide some debug analysis in this comment.
