Author: buildbot
Date: Tue Nov  5 00:41:31 2013
New Revision: 885446

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 Tue Nov  5 00:41:31 2013
@@ -218,7 +218,7 @@ camelContext.addComponent("activemq", ac
 
 <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>
+<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>maximumActive</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>maximumActiveSessionPerConnection</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 Tue Nov  5 
00:41:31 2013
@@ -224,7 +224,7 @@ camelContext.addComponent("activemq", ac
 
 <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>
+<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>maximumActive</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>maximumActiveSessionPerConnection</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>
 
@@ -345,50 +345,7 @@ droppable = false}
 <h3><a shape="rect" name="BookComponentAppendix-SeeAlso"></a>See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html" title="Configuring 
Camel">Configuring Camel</a></li><li><a shape="rect" href="component.html" 
title="Component">Component</a></li><li><a shape="rect" href="endpoint.html" 
title="Endpoint">Endpoint</a></li><li><a shape="rect" 
href="getting-started.html" title="Getting Started">Getting 
Started</a></li></ul>
 
-<h2><a shape="rect" 
name="BookComponentAppendix-ActiveMQJournalComponent"></a>ActiveMQ Journal 
Component</h2>
-
-<p>The ActiveMQ Journal Component allows messages to be stored in a rolling 
log file and then consumed from that log file.  The journal aggregates and 
batches up concurrent writes so that the overhead of writing and waiting for 
the disk sync is relatively constant regardless of how many concurrent writes 
are being done.  Therefore, this component supports and encourages you to use 
multiple concurrent producers to the same journal endpoint.</p>
-
-<p>Each journal endpoint uses a different log file and therefore write 
batching (and the associated performance boost) does not occur between multiple 
endpoints.</p>
-
-<p>This component only supports one active consumer on the endpoint.  After 
the message is processed by the consumer's processor, the log file is marked 
and only subsequent messages in the log file will get delivered to 
consumers.</p>
-
-
-<h3><a shape="rect" name="BookComponentAppendix-URIformat"></a>URI format</h3>
-
-<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
-<script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[
-activemq.journal:directoryName[?options]
-]]></script>
-</div></div>
-
-<p>So for example, to send to the journal located in the <tt>/tmp/data</tt> 
directory you would use the following URI:</p>
-
-<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
-<script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[
-activemq.journal:/tmp/data
-]]></script>
-</div></div>
-
-<h3><a shape="rect" name="BookComponentAppendix-Options"></a>Options</h3>
-<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" 
class="confluenceTh"> Name </th><th colspan="1" rowspan="1" 
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" 
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>syncConsume</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> If set to <tt>true</tt>, when the journal is marked after 
a message is consumed, wait till the Operating System has verified the mark 
update is safely stored on disk. </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>syncProduce</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> <tt>true</tt> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> If set to <tt>true</tt>, wait till the Operating System 
has verified the message is safely stored on disk. </td></tr></tbody></table>
-</div>
-</div>
-
-<p>You can append query options to the URI in the following format, 
<tt>?option=value&amp;option=value&amp;...</tt></p>
-
-<h3><a shape="rect" 
name="BookComponentAppendix-ExpectedExchangeDataTypes"></a>Expected Exchange 
Data Types</h3>
-
-<p>The consumer of a Journal endpoint generates <a shape="rect" 
class="external-link" 
href="http://activemq.apache.org/camel/maven/camel-core/apidocs/org/apache/camel/impl/DefaultExchange.html";>DefaultExchange</a>
 objects with the <a shape="rect" class="external-link" 
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html#getIn()">in
 message</a> :</p>
-<ul><li><a shape="rect" class="external-link" 
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html#getHeader(java.lang.String)">header</a>
 "journal" : set to the endpoint uri of the journal the message came 
from</li><li><a shape="rect" class="external-link" 
href="http://camel.apache.org/maven/current//camel-core/apidocs/org/apache/camel/Message.html#getHeader(java.lang.String)">header</a>
 "location" : set to a <a shape="rect" class="external-link" 
href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/kaha/impl/async/Location.html";>Location</a>
 which identifies where the recored was stored on disk</li><li><a shape="rect" 
class="external-link" 
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html#getBody()">body</a>
 : set to <a shape="rect" class="external-link" 
href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/util/ByteSequence.html";>ByteSequence</a
 > which contains the byte array data of the stored message</li></ul>
-
-
-<p>The producer to a Journal endpoint expects an <a shape="rect" 
class="external-link" 
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html";>Exchange</a>
 with an In message where the body can be converted to a <a shape="rect" 
class="external-link" 
href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/util/ByteSequence.html";>ByteSequence</a>
 or a byte[].</p>
-
-<h3><a shape="rect" name="BookComponentAppendix-SeeAlso"></a>See Also</h3>
-<ul><li><a shape="rect" href="configuring-camel.html" title="Configuring 
Camel">Configuring Camel</a></li><li><a shape="rect" href="component.html" 
title="Component">Component</a></li><li><a shape="rect" href="endpoint.html" 
title="Endpoint">Endpoint</a></li><li><a shape="rect" 
href="getting-started.html" title="Getting Started">Getting 
Started</a></li></ul>
-
+<div class="error"><span class="error">Unable to render {include}</span> 
Couldn't find a page to include called: ActiveMQ Journal</div>
 <h2><a shape="rect" name="BookComponentAppendix-AMQP"></a>AMQP</h2>
 
 

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 Tue Nov  5 00:41:31 
2013
@@ -21750,7 +21750,7 @@ camelContext.addComponent("activemq", ac
 
 <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>
+<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>maximumActive</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>maximumActiveSessionPerConnection</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.


Reply via email to