Client transaction context does not propagate with an asynchronous method invocation. From the Bean Developer’s view, there is never a transaction context flowing in from the client. This means, for example, that the semantics of the REQUIRED transaction attribute on an asynchronous method are exactly the same as REQUIRES_NEW.
Does this mean that when stateless calls async behavior is requries new but when async calls others behavior is normal? I have a long running batch step and when it fails and rollback it also rolls back failure traces we write in the db so I want it in a separate transaction so I figured async seems like nice fit but I am not sure if I need requires new or not? Cheers
