This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have a application made up of Spring/JPA/Hibernate. The JPA layer does the transaction handling. The application uses Glassfish jdbc connection pools.
In the logs there is an alarming amount of database calls setting autocommit to on then off. I believe this to be an issue between GF and mysql. Any pointers? Even if itcould be a problem with the applicatio any pointers for what to check for?
Im thinking should all webservice calls be annotated with @Transactional?
Even for selects the logs would show
the applicaton is clustered across a few instances of GF with 1 write database and a 5 readonly databases. If i can at least stop the autcommit changes on the readonly databases that would be a step forward. Im looking for pointers of what i could look into here as Im a bit confused
These setting on and off is takiing up alot of time on the database so if i can set readonly databases to default autocommit off (or on if needs be) databasse performance should improve