camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r880827 - in /websites/production/camel/content: activemq.html book-component-appendix.html book-in-one-page.html cache/main.pageCache
Date Wed, 02 Oct 2013 08:19:31 GMT
Author: buildbot
Date: Wed Oct  2 08:19:31 2013
New Revision: 880827

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/activemq.html
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache

Modified: websites/production/camel/content/activemq.html
==============================================================================
--- websites/production/camel/content/activemq.html (original)
+++ websites/production/camel/content/activemq.html Wed Oct  2 08:19:31 2013
@@ -204,12 +204,20 @@ camelContext.addComponent("activemq", ac
 <bean id="activemq" 
     class="org.apache.activemq.camel.component.ActiveMQComponent">
     <property name="configuration" ref="jmsConfig"/>
+
+    <!-- if we are using transacted then enable CACHE_CONSUMER (if not using XA) to
run faster
+         see more details at: http://camel.apache.org/jms
+    <property name="transacted" value="true"/>
+    <property name="cacheLevelName" value="CACHE_CONSUMER" />
+    -->
 </bean>
 ]]></script>
 </div></div>
 
 <div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Notice
the <b>init</b> and <b>destroy</b> methods on the pooled connection
factory. This is important to ensure the connection pool is properly started and shutdown.</td></tr></table></div>
 
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Important
information about when using transactions</b><br clear="none">If you are using
transactions then see more details at <a shape="rect" href="jms.html" title="JMS">JMS</a>.
And remember to set <tt>cacheLevelName</tt> to <tt>CACHE_CONSUMER</tt>
if you are not using XA transactions. This can dramatically improve performance.</td></tr></table></div>
+
 <p>The <tt>PooledConnectionFactory</tt> will then create a connection pool
with up to 8 connections in use at the same time. Each connection can be shared by many sessions.
There is an option named <tt>maxActive</tt> you can use to configure the maximum
number of sessions per connection; the default value is <tt>500</tt>. From <b>ActiveMQ
5.7</b> onwards the option has been renamed to better reflect its purpose, being named
as <tt>maxActiveSessionPerConnection</tt>. Notice the <tt>concurrentConsumers</tt>
is set to a higher value than <tt>maxConnections</tt> is. This is okay, as each
consumer is using a session, and as a session can share the same connection, we are in the
safe. In this example we can have 8 * 500 = 4000 active sessions at the same time.</p>
 
 <h3><a shape="rect" name="ActiveMQ-InvokingMessageListenerPOJOsinaCamelroute"></a>Invoking
MessageListener POJOs in a Camel route</h3>

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Wed Oct  2 08:19:31 2013
@@ -210,12 +210,20 @@ camelContext.addComponent("activemq", ac
 &lt;bean id="activemq" 
     class="org.apache.activemq.camel.component.ActiveMQComponent"&gt;
     &lt;property name="configuration" ref="jmsConfig"/&gt;
+
+    &lt;!-- if we are using transacted then enable CACHE_CONSUMER (if not using XA) to
run faster
+         see more details at: http://camel.apache.org/jms
+    &lt;property name="transacted" value="true"/&gt;
+    &lt;property name="cacheLevelName" value="CACHE_CONSUMER" /&gt;
+    --&gt;
 &lt;/bean&gt;
 ]]></script>
 </div></div>
 
 <div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Notice
the <b>init</b> and <b>destroy</b> methods on the pooled connection
factory. This is important to ensure the connection pool is properly started and shutdown.</td></tr></table></div>
 
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Important
information about when using transactions</b><br clear="none">If you are using
transactions then see more details at <a shape="rect" href="jms.html" title="JMS">JMS</a>.
And remember to set <tt>cacheLevelName</tt> to <tt>CACHE_CONSUMER</tt>
if you are not using XA transactions. This can dramatically improve performance.</td></tr></table></div>
+
 <p>The <tt>PooledConnectionFactory</tt> will then create a connection pool
with up to 8 connections in use at the same time. Each connection can be shared by many sessions.
There is an option named <tt>maxActive</tt> you can use to configure the maximum
number of sessions per connection; the default value is <tt>500</tt>. From <b>ActiveMQ
5.7</b> onwards the option has been renamed to better reflect its purpose, being named
as <tt>maxActiveSessionPerConnection</tt>. Notice the <tt>concurrentConsumers</tt>
is set to a higher value than <tt>maxConnections</tt> is. This is okay, as each
consumer is using a session, and as a session can share the same connection, we are in the
safe. In this example we can have 8 * 500 = 4000 active sessions at the same time.</p>
 
 <h3><a shape="rect" name="BookComponentAppendix-InvokingMessageListenerPOJOsinaCamelroute"></a>Invoking
MessageListener POJOs in a Camel route</h3>

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Oct  2 08:19:31 2013
@@ -21687,12 +21687,20 @@ camelContext.addComponent("activemq", ac
 &lt;bean id="activemq" 
     class="org.apache.activemq.camel.component.ActiveMQComponent"&gt;
     &lt;property name="configuration" ref="jmsConfig"/&gt;
+
+    &lt;!-- if we are using transacted then enable CACHE_CONSUMER (if not using XA) to
run faster
+         see more details at: http://camel.apache.org/jms
+    &lt;property name="transacted" value="true"/&gt;
+    &lt;property name="cacheLevelName" value="CACHE_CONSUMER" /&gt;
+    --&gt;
 &lt;/bean&gt;
 ]]></script>
 </div></div>
 
 <div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Notice
the <b>init</b> and <b>destroy</b> methods on the pooled connection
factory. This is important to ensure the connection pool is properly started and shutdown.</td></tr></table></div>
 
+<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Important
information about when using transactions</b><br clear="none">If you are using
transactions then see more details at <a shape="rect" href="jms.html" title="JMS">JMS</a>.
And remember to set <tt>cacheLevelName</tt> to <tt>CACHE_CONSUMER</tt>
if you are not using XA transactions. This can dramatically improve performance.</td></tr></table></div>
+
 <p>The <tt>PooledConnectionFactory</tt> will then create a connection pool
with up to 8 connections in use at the same time. Each connection can be shared by many sessions.
There is an option named <tt>maxActive</tt> you can use to configure the maximum
number of sessions per connection; the default value is <tt>500</tt>. From <b>ActiveMQ
5.7</b> onwards the option has been renamed to better reflect its purpose, being named
as <tt>maxActiveSessionPerConnection</tt>. Notice the <tt>concurrentConsumers</tt>
is set to a higher value than <tt>maxConnections</tt> is. This is okay, as each
consumer is using a session, and as a session can share the same connection, we are in the
safe. In this example we can have 8 * 500 = 4000 active sessions at the same time.</p>
 
 <h3><a shape="rect" name="BookInOnePage-InvokingMessageListenerPOJOsinaCamelroute"></a>Invoking
MessageListener POJOs in a Camel route</h3>

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.



Mime
View raw message