According to the Spring informat ion I don't think making a transaction read-only necessarily informs participants of the transaction, rather it's some optimization for the transaction manager to use. Maybe it just can just go through optimization in the logging or something like that?
Marking a transaction as read only has some nice performance
benefits as that can allow Hibernate/JPA to avoid some costly
operations. Also, I think it would be nice if the datasource
implementation could switch between actual connection pools based
on the read-only flag, to e.g. direct read-only queries to a
hot-standby instead of the primary database.
+1 from me for this!
Am 05.12.2022 um 18:08 schrieb arjan
Sounds useful to me indeed. Thanks for starting this.
I am new to this mailing list so maybe a few short words
to myself first: I am a Software Engineer in Germany
responsible for our JavaEE, soon to be JakartaEE
framework. I am quiet interested in JakartaEE and its
The topic I would like to discuss is the enhancement of
the @Transactional Annotation for JakartaEE 11. A good
template would be the Spring specific
Annotation of the same name which supports among
other things :
I already found a issue on github
regarding the Topic, which unfortunately has not seen any
attention given to it since 2016. So I wanted to spark a
In my opinion these enhancement could be quiet helpful.