In actuality I rewrote the tests and removed the
AbstractTransactionalJUnit4SpringContextTests super class and the
transactions worked. I also rewrote the the test as an integration test on a
tomcat server and confirmed that the transaction managers worked.
I did see the same javadoc comments
ChainedTransactionManager doesn't guarantee that both transactions will be
rolled back in both cases, here is a quote from JavaDoc:
Using this implementation assumes that errors causing a transaction rollback
will usually happen before the transaction completion or during the commit
of the *most
