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

(cherry picked from commit 2303a76e2cb92ef0bcf282851c9cf1db4fd2eb00)


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/8e874ce5
Tree: http://git-wip-us.apache.org/repos/asf/qpid-broker-j/tree/8e874ce5
Diff: http://git-wip-us.apache.org/repos/asf/qpid-broker-j/diff/8e874ce5

Branch: refs/heads/7.0.x
Commit: 8e874ce58909896cbc4985aaab2957eca6023b0c
Parents: ba4344f
Author: Alex Rudyy <oru...@apache.org>
Authored: Mon Feb 19 17:30:51 2018 +0000
Committer: Alex Rudyy <oru...@apache.org>
Committed: Mon Feb 19 23:19:57 2018 +0000

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


http://git-wip-us.apache.org/repos/asf/qpid-broker-j/blob/8e874ce5/doc/java-broker/src/docbkx/runtime/Java-Broker-Runtime-Transaction-Timeout.xml
----------------------------------------------------------------------
diff --git 
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
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 connection
-    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 JMS
-    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 producer
+    or consumer will cause the connection to be closed - this disconnecting 
all producers and consumers
+    created on that connection.</para>
   </section>
  </section>
 </section>


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

Reply via email to