qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oru...@apache.org
Subject qpid-broker-j git commit: QPID-8091: [Broker-J] Correct transaction timeout documentation
Date Mon, 19 Feb 2018 17:34:11 GMT
Repository: qpid-broker-j
Updated Branches:
  refs/heads/master 3aad3e3d3 -> 2303a76e2

QPID-8091: [Broker-J] Correct transaction timeout documentation

Project: http://git-wip-us.apache.org/repos/asf/qpid-broker-j/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-broker-j/commit/2303a76e
Tree: http://git-wip-us.apache.org/repos/asf/qpid-broker-j/tree/2303a76e
Diff: http://git-wip-us.apache.org/repos/asf/qpid-broker-j/diff/2303a76e

Branch: refs/heads/master
Commit: 2303a76e2cb92ef0bcf282851c9cf1db4fd2eb00
Parents: 3aad3e3
Author: Alex Rudyy <orudyy@apache.org>
Authored: Mon Feb 19 17:30:51 2018 +0000
Committer: Alex Rudyy <orudyy@apache.org>
Committed: Mon Feb 19 17:32:32 2018 +0000

 .../runtime/Java-Broker-Runtime-Transaction-Timeout.xml | 12 +++---------
 1 file changed, 3 insertions(+), 9 deletions(-)

diff --git a/doc/java-broker/src/docbkx/runtime/Java-Broker-Runtime-Transaction-Timeout.xml
index f250364..421234b 100644
--- a/doc/java-broker/src/docbkx/runtime/Java-Broker-Runtime-Transaction-Timeout.xml
+++ b/doc/java-broker/src/docbkx/runtime/Java-Broker-Runtime-Transaction-Timeout.xml
@@ -97,15 +97,9 @@ CON-1002 : Close : Open transaction timed out
    <para>It is impossible to give suggested values, due to the large variation in usage
depending on
     the applications using a broker. However, clearly transactions should not span the expected
     lifetime of any client application as this would indicate a hung client.</para>
-   <para>When configuring warning and closure timeouts, it should be noted that these
only apply to
-    message producers that are connected to the broker, but that a timeout will cause the
-    to be closed - this disconnecting all producers and consumers created on that connection.</para>
-   <para>This should not be an issue for environments using Mule or Spring, where connection
-    factories can be configured appropriately to manage a single MessageProducer object per
-    Session and Connection. Clients that use the JMS API directly should be aware that sessions
-    managing both consumers and producers, or multiple producers, will be affected by a single
-    producer hanging or leaving a transaction idle or open, and closed, and must take appropriate
-    action to handle that scenario.</para>
+   <para>When configuring closure timeouts, it should be noted that a timeout on any
+    or consumer will cause the connection to be closed - this disconnecting all producers
and consumers
+    created on that connection.</para>

To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org

View raw message