<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=costin" rel="nofollow">Costin Leau</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-8334?redirect=false" rel="nofollow">SPR-8334</a></strong> and commented</p>
<p dir="auto">SimpleCacheManager and MapCacheManager are identical and one of them should be eliminated.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.1 M1</p>
<p dir="auto"><strong>Referenced from:</strong> commits <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/spring-projects/spring-framework/commit/700a02b094921d223e1bbc3bcccf8a1f9bc4febe/hovercard" href="https://github.com/spring-projects/spring-framework/commit/700a02b094921d223e1bbc3bcccf8a1f9bc4febe"><tt>700a02b</tt></a>, <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/spring-projects/spring-framework/commit/cc519e7c6d6a74e1549a08f57a0929de02bad0a9/hovercard" href="https://github.com/spring-projects/spring-framework/commit/cc519e7c6d6a74e1549a08f57a0929de02bad0a9"><tt>cc519e7</tt></a></p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=david_syer" rel="nofollow">Dave Syer</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-3156?redirect=false" rel="nofollow">SPR-3156</a></strong> and commented</p>
<p dir="auto">Docos (or maybe assertion in code) to help with using DefaultMessageListenerContainer with non-XA transaction manager.  It is actually quite plausible (and common) to use a DefaultMessageListenerContainer with a DataSourceTransactionManager (not full XA).  Then database work done in the listener can rollback, but will guarantee a message rollback <strong>only</strong> if transactedSession=true.  If the flag is true the worst that can happen is a duplicate message if the database commits, and the commit of the JMS session fails (power failure etc.).  But the default is false, so you can get duplicate messages whatever happens with the datasource.  It would help if the docos mentioned this scenario, or provided some protection (e.g. if the transaction manager is not JtaTranasactionManager, then make sure transactedSession=true).</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.0.2</p>