Update JMS documentation

This commit updates the JMS documentation regarding the side effects
of not using the  cache with a non durable subscriber.

Issue: SPR-7883

src/asciidoc/index.adoc

@@ -40583,6 +40583,11 @@ This listener container strikes a good balance between low requirements on the J
 provider, advanced functionality such as transaction participation, and compatibility
 with Java EE environments.
 
+The cache level of the container can be customized. Note that when no caching is enabled,
+a new connection and a new session is created for each message reception. Combining this
+with a non durable subscription with high loads may lead to message lost. Make sure to
+use a proper cache level in such case.
+
 This container also has recoverable capabilities when the broker goes down. By default,
 a simple `BackOff` implementation retries every 5 seconds. It is possible to specify
 a custom `BackOff` implementation for more fine-grained recovery options, see