Project: mule
Issue MULE-7354: Selector watermark is not thread safe
When using watermark with a selector, the same selector instance is reused across invocations which means that if two polls are executed concurrently values would be overwritten. Right now this is a non issue because watermark only runs on synchronous flows. However, it makes affects code reusability and this will potentially break if we decide to support async watermark or if CloudHub centralised scheduler decides to fire concurrently for different tenants
Story points: 2