When a (transactional) method of an EJB calls another (transactional) method of another EJB, and an exception is thrown in the second, but catched in the first one, it seems tha
Yes, it's true, if the exception is a runtime exception. Checked exceptions don't cause a transaction rollback.
To avoid it, just make sure that the code in methodB
doesn't throw any runtime exception. A runtime exception normally indicates a bug, or a state which doesn't allow for continuing the work.