[jboss-cvs] JBoss Messaging SVN: r7040 - in trunk: examples/javaee/mdb/server and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 26 13:52:48 EDT 2009
Author: ataylor
Date: 2009-05-26 13:52:48 -0400 (Tue, 26 May 2009)
New Revision: 7040
Modified:
trunk/docs/user-manual/en/configuration-index.xml
trunk/docs/user-manual/en/using-jms.xml
trunk/examples/javaee/mdb/server/jbm-configuration.xml
Log:
more doc updates
Modified: trunk/docs/user-manual/en/configuration-index.xml
===================================================================
--- trunk/docs/user-manual/en/configuration-index.xml 2009-05-26 17:13:21 UTC (rev 7039)
+++ trunk/docs/user-manual/en/configuration-index.xml 2009-05-26 17:52:48 UTC (rev 7040)
@@ -770,7 +770,8 @@
<entry/>
</row>
<row>
- <entry>connection-factory.client-id</entry>
+ <entry><link linkend="using-jms.clientid"
+ >connection-factory.client-id</link></entry>
<entry>String</entry>
<entry>The pre-configured client ID for the connection factory.</entry>
<entry>null</entry>
@@ -877,14 +878,16 @@
<entry>false</entry>
</row>
<row>
- <entry>connection-factory.dups-ok-batch-size</entry>
+ <entry><link linkend="dups-ok-batch-size"
+ >connection-factory.dups-ok-batch-size</link></entry>
<entry>int</entry>
<entry>The batch size in bytes between acknowledgements when using
DUPS_OK_ACKNOWLEDGE mode</entry>
<entry>1024 * 1024</entry>
</row>
<row>
- <entry>connection-factory.transaction-batch-size</entry>
+ <entry><link linkend="using-jms.txbatchsize"
+ >connection-factory.transaction-batch-size</link></entry>
<entry>int</entry>
<entry>The batch size in bytes between acknowledgements when using a
transactional session</entry>
Modified: trunk/docs/user-manual/en/using-jms.xml
===================================================================
--- trunk/docs/user-manual/en/using-jms.xml 2009-05-26 17:13:21 UTC (rev 7039)
+++ trunk/docs/user-manual/en/using-jms.xml 2009-05-26 17:52:48 UTC (rev 7040)
@@ -10,7 +10,7 @@
<para>JBoss Messaging also ships with a wide range of examples, many of which demonstrate JMS
API usage. A good place to start would be to play around with the simple JMS Queue and Topic
example, but we also provide examples for many other parts of the JMS API. A full
- description of the examples is available in <xref linkend="examples" />.</para>
+ description of the examples is available in <xref linkend="examples"/>.</para>
<para>In this section we'll go through the main steps in configuring the server for JMS and
creating a simple JMS program. We'll also show how to configure and use JNDI, and also how
to use JMS with JBoss Messaging without using any JNDI.</para>
@@ -25,8 +25,8 @@
queue.</para>
<para>The queue will be a <literal>durable</literal> queue, i.e. it will survive a server
restart or crash. We also want to predeploy the queue, i.e. specify the queue in the
- server JMS configuration so it's created automatically without us having to explicitly create
- it from the client.</para>
+ server JMS configuration so it's created automatically without us having to explicitly
+ create it from the client.</para>
</section>
<section id="using-jms.server.configuration">
<title>JMS Server Configuration</title>
@@ -38,7 +38,8 @@
configuration parameters. In most cases the defaults will be acceptable.</para>
<para>We'll deploy a single JMS Queue and a single JMS Connection Factory instance on the
server for this example but there are no limits to the number of Queues, Topics and
- Connection Factory instances you can deploy from the file. Here's our configuration:</para>
+ Connection Factory instances you can deploy from the file. Here's our
+ configuration:</para>
<programlisting>
<configuration xmlns="urn:jboss:messaging"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -145,12 +146,12 @@
<para>With JBoss Messaging you can do exactly that. JBoss Messaging supports the direct
instantiation of JMS Queue, Topic and Connection Factory instances, so you don't have to
use JNDI at all.</para>
- <para>For a full working example of direct instantiation please see the JMS examples in <xref
- linkend="examples" />.</para>
+ <para>For a full working example of direct instantiation please see the JMS examples in
+ <xref linkend="examples"/>.</para>
<para>Here's our simple example, rewritten to not use JNDI at all:</para>
<para>We create the JMS ConnectionFactory object directly, note we need to provide
connection parameters and specify which transport we are using, for more information on
- connectors please see <xref linkend="configuring-transports" />.</para>
+ connectors please see <xref linkend="configuring-transports"/>.</para>
<programlisting>
TransportConfiguration transportConfiguration =
new TransportConfiguration(NettyConnectorFactory.class.getName());
@@ -177,4 +178,27 @@
System.out.println("Got order: " + receivedMessage.getText());
</programlisting>
</section>
+ <section id="using-jms.clientid">
+ <title>Setting The Client ID</title>
+ <para>This represents the client id for a JMS client and is needed for creating durable
+ subscriptions. It is possible to configure this on the connection factory and can be set
+ via the <literal>client-id</literal> element. Any connection created by this connection
+ factory will have this set as its client id.</para>
+ </section>
+ <section id="using-jms.dupsokbatchsize">
+ <title>Setting The Batch Size for DUPS_OK </title>
+ <para>When the JMS acknowledge mode is set to <literal>DUPS_OK</literal> it is possible to
+ configure the consumer so that it sends the acknowledgements in batches rather that one
+ at a time, saving valuable bandwidth. This can be configured via the connection factory
+ via the <literal>dups-ok-batch-size</literal> element and is set in bytes. The default
+ is 1024 * 1024.</para>
+ </section>
+ <section id="using-jms.txbatchsize">
+ <title>Setting The Transaction Batch Size</title>
+ <para>When receiving messages in a transaction it is possible to configure the consumer to
+ send acknowledgements in batches rather than individually saving valuable bandwidth.
+ This can be configured on the connection factory via the <literal
+ >transaction-batch-size</literal> element and is set in bytes. The default is 1024 *
+ 1024.</para>
+ </section>
</chapter>
Modified: trunk/examples/javaee/mdb/server/jbm-configuration.xml
===================================================================
--- trunk/examples/javaee/mdb/server/jbm-configuration.xml 2009-05-26 17:13:21 UTC (rev 7039)
+++ trunk/examples/javaee/mdb/server/jbm-configuration.xml 2009-05-26 17:52:48 UTC (rev 7040)
@@ -6,6 +6,8 @@
<connectors>
<connector name="netty">
<factory-class>org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</factory-class>
+ <param key="jbm.remoting.netty.host" value="${jbm.remoting.netty.host:localhost}" type="String"/>
+ <param key="jbm.remoting.netty.port" value="${jbm.remoting.netty.port:5445}" type="Integer"/>
</connector>
<connector name="in-vm">
@@ -25,7 +27,8 @@
<!-- Netty TCP Acceptor -->
<acceptor name="netty">
<factory-class>org.jboss.messaging.integration.transports.netty.NettyAcceptorFactory</factory-class>
- <param key="jbm.remoting.netty.port" value="${jbm.remoting.netty.port}" type="Integer"/>
+ <param key="jbm.remoting.netty.host" value="${jbm.remoting.netty.host:localhost}" type="String"/>
+ <param key="jbm.remoting.netty.port" value="${jbm.remoting.netty.port:5445}" type="Integer"/>
</acceptor>
</acceptors>
More information about the jboss-cvs-commits
mailing list