[jboss-cvs] JBoss Messaging SVN: r7724 - in trunk: examples/jms/paging and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 13 13:49:23 EDT 2009
Author: clebert.suconic at jboss.com
Date: 2009-08-13 13:49:22 -0400 (Thu, 13 Aug 2009)
New Revision: 7724
Modified:
trunk/docs/user-manual/en/paging.xml
trunk/examples/jms/paging/readme.html
trunk/examples/jms/paging/server0/jbm-configuration.xml
Log:
few tweaks on paging documentation
Modified: trunk/docs/user-manual/en/paging.xml
===================================================================
--- trunk/docs/user-manual/en/paging.xml 2009-08-13 13:24:09 UTC (rev 7723)
+++ trunk/docs/user-manual/en/paging.xml 2009-08-13 17:49:22 UTC (rev 7724)
@@ -19,7 +19,8 @@
<section id="paging.main.config">
<title>Configuration</title>
<para>You can configure the location of the paging folder</para>
- <para>Global paging parameters are specified on the main configuration file.</para>
+ <para>Global paging parameters are specified on the main configuration file (<literal
+ >jbm-configuration.xml</literal>).</para>
<programlisting><configuration xmlns="urn:jboss:messaging"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:jboss:messaging /schema/jbm-configuration.xsd">
@@ -58,17 +59,17 @@
</section>
<section id="paging.mode">
<title>Paging Mode</title>
- <para>As soon as messages
- delivered to an address exceed the configured size, that address alone goes into page
- mode.</para>
+ <para>As soon as messages delivered to an address exceed the configured size, that address
+ alone goes into page mode.</para>
<section>
<title>Configuration</title>
- <para>Configuration is done at the address settings.</para>
+ <para>Configuration is done at the address settings, done at the main configuration file
+ (<literal>jbm-configuration.xml</literal>).</para>
<programlisting> <address-settings>
<address-setting match="jms.someaddress">
- <max-size-bytes>-1</max-size-bytes>
+ <max-size-bytes>104857600</max-size-bytes>
<page-size-bytes>10485760</page-size-bytes>
- <drop-messages-when-full>true</drop-messages-when-full>
+ <drop-messages-when-full>false</drop-messages-when-full>
</address-setting>
</address-settings>
</programlisting>
Modified: trunk/examples/jms/paging/readme.html
===================================================================
--- trunk/examples/jms/paging/readme.html 2009-08-13 13:24:09 UTC (rev 7723)
+++ trunk/examples/jms/paging/readme.html 2009-08-13 17:49:22 UTC (rev 7724)
@@ -1,13 +1,13 @@
<html>
<head>
<title>JBoss Messaging Paging Example</title>
- <link rel="stylesheet" type="text/css" href="../../common/common.css">
+ <link rel="stylesheet" type="text/css" href="../../common/common.css"/>
</head>
<body>
<h1>Paging Example</h1>
<br>
<p>This example shows how JBoss Messaging would avoid running out of resources by paging messages.</p>
- <p>A maxSize could be specified per Destination on the destinations settings, or a globalMaxSize could also be set on the maing config file.</a>
+ <p>A maxSize could be specified per Destination on the destinations settings (jbm-configuration.xml).</p>
<p>When the buffered messages are consuming too much memory, JBossMessaging starts writing messages on the file-system, and as the memory is released by message acknowledgement or transaction commits those messages are recovered from disk and placed in memory</p>
<p>Acknowledgement plays an important factor on paging as messages will stay on the file system until the memory is released</p>
Modified: trunk/examples/jms/paging/server0/jbm-configuration.xml
===================================================================
--- trunk/examples/jms/paging/server0/jbm-configuration.xml 2009-08-13 13:24:09 UTC (rev 7723)
+++ trunk/examples/jms/paging/server0/jbm-configuration.xml 2009-08-13 17:49:22 UTC (rev 7724)
@@ -9,6 +9,7 @@
</connector>
</connectors>
+ <paging-directory>./data/page</paging-directory>
<!-- Acceptors -->
<acceptors>
More information about the jboss-cvs-commits
mailing list