Posted in JDBC, Spring, tagged readOnly, Spring, transaction management, transaction optimization, transaction strategies on February 22, 2009 | Leave a Comment »
This article is a small POC on how the readOnly attribute used in Spring Transaction strategy improves database access in case of transactions that involve only READing data from datasources.
First a small extract from the Spring reference documentation:
The TransactionDefinition interface specifies:
• Isolation: the degree of isolation this transaction has from the work of other transactions. For [...]
Posted in JAVA, Spring, tagged checked exception, Spring, transaction management, transaction strategies, tx, unchecked exception on February 17, 2009 | Leave a Comment »
I have been using Spring TX Management for quite sometime until I recently came upon an article describing the common pitfalls that occur in Transaction Strategies. Although many cases were covered, I would like to describe the common one that is seen in most code.
I am going to explain it with the help of a [...]
Posted in JAVA, Quartz, Spring, tagged Concurrent, JAVA, Quartz, Spring, Thread on October 31, 2008 | 1 Comment »
In one of our current integration projects, where we were using Spring, we had a Spring bean which was constantly running every 20 to 30 seconds pooling the database and fetching new status of records. These statuses would be constantly sent to our client as and when new status came up. This Spring bean is [...]
