Matthias Kuhr

Hi Mapobo, thanks for reaching out! You are correct, the SDK filters currently don't support async. You could work around this by writing a custom filter that does it, but...

Okay, so when using a destination the thread context may or may not be needed. It depends if your destination is related to a specific tenant or user. Is this...

Happy to hear that it works for your use case! WRT the async servlet support, this seems to be supported: https://answers.sap.com/questions/9831334/servlet-30-async-support.html Maybe just give it a try :)

Hey, unfortunately we didn't get around to implementing this, and we currently don't have it planned. But as you might have seen, we [moved the SDK to open source](https://github.com/SAP/cloud-sdk-java) in...

Interesting, okay. In that case we anyway should be careful with implementing anything in the SDK, as we aim to only offer OOTB functionality for things that are conforming to...

> it would send all fields and that is not supported by the B1 service? Naively, I'd think updating all properties is just a special case of updating some properties...

Happy that it worked 🥳 Also, I didn't know about the `retainAll` you used above before, that's pretty handy, will use it myself if I can remember 😄

Hi Akash, hitting the api locally with significant load and not yielding a failure makes me think the error might come from somewhere else. You see, the connection pool is...

Please provide the information as described in the issue template: full stack trace, logs etc. Also, please upgrade to the latest version 5.11.0

Closing, assuming the issue is resolved