Doc: JMS CachingConnectionFactory incompatible with DefaultMessageListenerContainer in some circumstances [SPR-10581]

[spring-projects-issues]

Daniel Blezek opened SPR-10581 and commented

Using a CachingConnectionFactory in conjunction with a DefaultMessageListenerContainer that implements scaling using maxMessagePerTask can result in JMS messages delivered to cached consumers that are no longer attached to the DefaultMessageListenerContainer. This problem is documented and explained in detail in this forum thread: http://forum.springsource.org/showthread.php?133467-DMLC-maxMessagesPerTask-causes-inability-to-scale-down

Suggested Fix:

Put a comment in the documentation that consumer caching is not compatible with dynamic scaling in DefaultMessageListenerContainer OR issue a warning when a developer attempts to use them together.

---

Affects: 3.2 GA

Reference URL: http://forum.springsource.org/showthread.php?133467-DMLC-maxMessagesPerTask-causes-inability-to-scale-down

[spring-projects-issues]

Juergen Hoeller commented

I've added a warning to DMLC's javadoc for the time being.

We could try to detect a mismatch in configuration at runtime but I'd rather not go that far at this point, since there is always the risk of overreacting to configuration that is perfectly valid within its custom context...

Juergen