Improving Logging in the Message Helper Component to Track Synapse Message Context Properties with OM-Type Elements

[sajith-madhusanka]

Current Limitation

We have recently identified that when a Property mediator is configured to store an OM-type element in the Synapse message context before an Iterator/ForEach mediator—which performs message context cloning—it can have a performance impact, as it increases both memory and CPU consumption. This is because the OM object is built during each message context cloning attempt, requiring more memory when the OM object is large and has a deep XML structure. We can address this issue by storing the relevant property in the Axis2 message context instead of the Synapse message context. However, to do this, we need to identify which property is causing the issue, and currently, it is a bit difficult to determine that.

Suggested Improvement

Enhance the logging mechanism of the relevant component to track the Property mediator responsible for setting the OM-type element in the Synapse message context. Introducing debug-level logs would be sufficient for this purpose.

Version

4.1.0