After switching to a WebSphere-defined datasource I am getting the error "LocalTransaction rolled-back due to setRollbackOnly". The link http://www-1.ibm.com/support/docview...id=swg21141640 explains this, but we are using Spring + Hibernate and need a Spring-level control to overcome this problem.
The WebSphere approach of changing a property on all the servlets is very difficult, error-prone and a maintenance nightmare.
One post I saw suggested a Hibernate workaround of setting a property on the transactionManager be to force a commit, but that syntax doesn't seem to be allowed in our version.
Is there some way we can tell Spring (or Hibernate) to force autocommit on the sessions?