|License Type||SaaS & On-Premise|
|Main Product Category||Java Agent|
WARN - Ignoring propagator base-io-18 because maximum reached
These can occur when we are tracking a dataflow through the app. The Agent sees data passed from function, to function, to function, to function without reaching a sink enough times to hit our limiter. By default that limiter is 100, so if a dataflow had over 100 events when you viewed it in the Details tab in TeamServer, we just wouldn’t report it - this limiter’s primarily there for performance reasons. When a dataflow is that long, it’s extremely complex and so the risk of it being exploited is much lower.
This can be increased with an agent property. (default is 100) Setting a value of 200 can clear most occurrences.
Environment Variable: CONTRAST__ASSESS__MAX_PROPAGATION_EVENTS
System Property: -Dcontrast.assess.max_propagation_events
These can also be safely ignored by setting log level to ERROR only.
Environment Variable: CONTRAST__AGENT__LOGGER__LEVEL=ERROR
System Property: -Dcontrast.agent.logger.level=ERROR
More information on Java agent configuration can be seen here in our documentation.