Different EntityManager context behavior between SimpleJpaRepository methods and derived query methods when using separate Rw/Ro EntityManagers inside a @Transactional boundary

[qkrtkdwns3410]

@christophstrobl

#4107

I apologize for the interruption, but I would really appreciate
it if you could clarify whether this behavior — the difference
in EntityManager lifecycle between SimpleJpaRepository methods
(e.g., findById) and derived query methods — is intentional
or considered a bug.

Any guidance would be greatly appreciated. Thank you!