Which context are you using @In with? Be careful because some restrictions apply with @Asynchronous (as stated in 22.2.1. Asynchronous methods)
The asynchronous method is processed in a completely new event context and does not have access to the session or conversation context state of the caller. However, the business process context is propagated.
that was the problem indeed. Solved by providing the component as arguments to the async method.