Author: shawkins
Date: 2010-08-23 13:53:50 -0400 (Mon, 23 Aug 2010)
New Revision: 2484
Modified:
branches/7.1.x/documentation/client-developers-guide/src/main/docbook/en-US/content/jdbc-connection.xml
Log:
TEIID-1211 updating the load balancing doc
Modified:
branches/7.1.x/documentation/client-developers-guide/src/main/docbook/en-US/content/jdbc-connection.xml
===================================================================
---
branches/7.1.x/documentation/client-developers-guide/src/main/docbook/en-US/content/jdbc-connection.xml 2010-08-23
17:44:19 UTC (rev 2483)
+++
branches/7.1.x/documentation/client-developers-guide/src/main/docbook/en-US/content/jdbc-connection.xml 2010-08-23
17:53:50 UTC (rev 2484)
@@ -532,6 +532,8 @@
The default setting is to maintain 16 connections (see
<code>org.teiid.sockets.maxCachedInstances</code> in the client jar's
teiid-client-settings.properties file.
If you're client is connecting to large numbers of Teiid instances and
you're using post connection time load balancing, then consider increasing the number
of cached instances.
You may either set an analogous system property or create another version of
teiid-client-settings.properties file and place it into the classpath ahead of the client
jar.</para>
+ <note><para>Session level temporary tables, currently running
transactions, session level cache entries, and PreparedPlans for a given session will not
be available on other cluster members.
+ Therefore, it is recommended that post connection time load balancing is only
used when the logical connection could have been closed, but the actual connection is
reused (the typical connection pool pattern).</para></note>
</section>
<section id="advancedconfig">
<title>Advanced Configuration</title>
Show replies by date