[jboss-cvs] JBoss Messaging SVN: r4340 - in trunk: examples/jms/config and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 29 11:18:54 EDT 2008
Author: ataylor
Date: 2008-05-29 11:18:54 -0400 (Thu, 29 May 2008)
New Revision: 4340
Modified:
trunk/docs/userguide/en/modules/configuration.xml
trunk/docs/userguide/en/modules/installation.xml
trunk/examples/jms/config/jndi.properties
trunk/src/config/jbm-jndi.xml
Log:
updated configuration and updated docs
Modified: trunk/docs/userguide/en/modules/configuration.xml
===================================================================
--- trunk/docs/userguide/en/modules/configuration.xml 2008-05-29 14:52:18 UTC (rev 4339)
+++ trunk/docs/userguide/en/modules/configuration.xml 2008-05-29 15:18:54 UTC (rev 4340)
@@ -122,8 +122,12 @@
<journal-type>asyncio</journal-type>
- <journal-sync>true</journal-sync>
+ <!-- Does the journal sync to disk on each transaction commit, prepare or rollback? -->
+ <journal-sync-transactional>true</journal-sync-transactional>
+ <!-- Does the journal sync to disk for every non transactional persistent operation? -->
+ <journal-sync-non-transactional>false</journal-sync-non-transactional>
+
<journal-file-size>10485760</journal-file-size>
<journal-min-files>10</journal-min-files>
@@ -253,13 +257,20 @@
</para>
</listitem>
<listitem>
- <para>journal-sync</para>
- <para>Whether or not to allow the synch to disk on commit and rollback. false will only write to the OS
- buffers
- and lets the OS deal with synching
+ <para>journal-sync-transactional</para>
+ <para>Whether or not to synch to disk for a transaction on commit, prepare or rollback. false will only
+ write to the OS
+ buffers and lets the OS deal with synching
</para>
</listitem>
<listitem>
+ <para>journal-sync-non-transactional</para>
+ <para>Whether or not to synch to disk for every non transaction persistent operation. false will only write
+ to the OS
+ buffers and lets the OS deal with synching
+ </para>
+ </listitem>
+ <listitem>
<para>journal-file-size</para>
<para>The size of the data file to create, these files are pre-allocated and filled as needed.</para>
</listitem>
@@ -536,34 +547,24 @@
<entry name="/acme/MyExampleConnectionFactoryDupe"/>
<entry name="java:/xyz/CF1"/>
<entry name="java:/connectionfactories/acme/connection_factory"/>
- <!-- You can specify the default Client ID to use for connections created
- using this factory -->
+ <!-- You can specify the default Client ID to use for connections created using this factory -->
<client-id>MyClientID</client-id>
- <!-- PrefetchSize determines the maximum number of messages the client consumer
- will buffer locally -->
- <prefetch-size>150</prefetch-size>
<!-- The batch size to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode -->
- <dups-ok-batch-size>5000</dups-ok-batch-size>
- <!-- Does this connection factory support automatic failover? -->
- <supports-failover>false</supports-failover>
- <!-- Does this connection factory support automatic client side load balancing? -->
- <supports-load-balancing>false</supports-load-balancing>
- <!-- The class name of the factory used to create the load balancing policy to
- use on the client side -->
- <load-balancing-factory>
- org.jboss.messaging.jms.client.plugin.RoundRobinLoadBalancingFactory
- </load-balancing-factory>
- <!-- Whether we should be strict TCK compliant, i.e. how we deal with foreign messages,
- defaults to false-->
- <strict-tck>true</strict-tck>
-
- <!-- This is the window size in number of messages to use when using producer
- window based flow control -->
+ <dups-ok-batch-size>5000</dups-ok-batch-size>-size>
+ <!-- This is the window size in number of messages to use when using producer window based flow control -->
<producer-window-size>1000</producer-window-size>
-
- <!-- This is the maximum producer send rate that will be applied when using
- rate based producer flow control -->
+ <!-- This is the maximum producer send rate that will be applied when using rate based producer flow control -->
<producer-max-rate>100</producer-max-rate>
+ <!-- This is the window size in number of messages to use when using consumer window based flow control -->
+ <consumer-window-size>1000</consumer-window-size>
+ <!-- This is the maximum producer send rate that will be applied when using rate based consumer flow control -->
+ <consumer-max-rate>5000</consumer-max-rate>
+ <!--Whether or not we use a blocking call when acknowledging a message-->
+ <block-on-acknowledge>false</block-on-acknowledge>
+ <!--Whether we send non persistent messages synchronously-->
+ <send-np-messages-synchronously>true</send-np-messages-synchronously>
+ <!--Whether we send persistent messages synchronously-->
+ <send-p-messages-synchronously>true</send-p-messages-synchronously>
</connection-factory>
@@ -648,37 +649,45 @@
<para>The client id for connections created using this Connection Factory</para>
</listitem>
<listitem>
- <para>prefetch-size</para>
- <para>The maximum number of messages a consumer can buffer locally</para>
- </listitem>
- <listitem>
<para>dups-ok-batch-size</para>
<para>The number of acks to batch up when DUPS_OK_ACKNOWLEDGE acknowledgement mode is used</para>
</listitem>
<listitem>
- <para>supports-failover</para>
- <para>Does the Connection Factory support failover, currently disabled.</para>
+ <para>producer-window-size</para>
+ <para>This is the window size in number of messages to use when using producer window based flow
+ control
+ </para>
</listitem>
<listitem>
- <para>supports-load-balancing</para>
- <para>Does the Connection Factory support load balancing, currently disabled</para>
+ <para>producer-max-rate</para>
+ <para>This is the maximum producer send rate that will be applied when using rate based producer flow
+ control.
+ </para>
</listitem>
<listitem>
- <para>load-balancing-factory</para>
- <para>The class to use for creating the load balancing class, currently not used.</para>
+ <para>consumer-window-size</para>
+ <para>This is the window size in number of messages to use when using consumer window based flow
+ control
+ </para>
</listitem>
<listitem>
- <para>strict-tck</para>
- <para>Whether strict tck shoul dbe adhered to</para>
+ <para>consumer-max-rate</para>
+ <para>This is the maximum producer send rate that will be applied when using rate based consumer flow
+ control.
+ </para>
</listitem>
<listitem>
- <para>producer-window-size</para>
- <para>The window size when producer window based flow control is enabled.</para>
+ <para>block-on-acknowledge</para>
+ <para>Whether or not we use a blocking call when acknowledging a message</para>
</listitem>
<listitem>
- <para>producer-max-rate</para>
- <para>The max rate when producer rate based flow control is enabled.</para>
+ <para>send-np-messages-synchronously</para>
+ <para>Whether we send non persistent messages synchronously.</para>
</listitem>
+ <listitem>
+ <para>send-p-messages-synchronously</para>
+ <para>Whether we send persistent messages synchronously.</para>
+ </listitem>
</itemizedlist>
</listitem>
<listitem>
Modified: trunk/docs/userguide/en/modules/installation.xml
===================================================================
--- trunk/docs/userguide/en/modules/installation.xml 2008-05-29 14:52:18 UTC (rev 4339)
+++ trunk/docs/userguide/en/modules/installation.xml 2008-05-29 15:18:54 UTC (rev 4340)
@@ -36,7 +36,7 @@
</listitem>
<listitem>
<para>docs</para>
- <para>This contains this user guide and the JBM Javadocs..
+ <para>This contains this user guide and the JBM Javadocs..
</para>
</listitem>
<listitem>
@@ -47,7 +47,8 @@
</listitem>
</itemizedlist>
<para>To run JBM, open up a shell or command prompt and navigate into the 'bin' directory. Then execute './run.sh'
- (or 'run.bat' on windows) and you should see the following output</para>
+ (or 'run.bat' on windows) and you should see the following output
+ </para>
<programlisting>
java -Xmx512M -Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.core
.logging.JBMLoggerPlugin -Djava.library.path=. -classpath ../lib/xercesImpl.j
@@ -62,105 +63,107 @@
n-core.jar:../lib/jboss-aop-mc-int.jar:../lib/jboss-aop-jdk50.jar:../lib/java
ssist.jar:../lib/concurrent.jar:../lib/commons-logging.jar:../config/ org.jbo
ss.jms.server.microcontainer.JBMBootstrapServer jbm-standalone-beans.xml
- 10:25:57,225 INFO @main [JournalStorageManager] Directory /home/andy/jbm-tes
+ 10:25:57,225 INFO @main [JournalStorageManager] Directory /home/andy/jbm-tes
t/data/bindings does not already exists
- 10:25:57,226 INFO @main [JournalStorageManager] Creating it
- 10:25:57,270 INFO @main [JournalStorageManager] Directory /home/andy/jbm-tes
+ 10:25:57,226 INFO @main [JournalStorageManager] Creating it
+ 10:25:57,270 INFO @main [JournalStorageManager] Directory /home/andy/jbm-tes
t/data/journal does not already exists
- 10:25:57,271 INFO @main [JournalStorageManager] Creating it
- 10:25:57,276 INFO @main [JournalStorageManager] AIO loaded successfully
- 10:25:57,689 INFO @main [MinaService] Registering:tcp://localhost:5400
- 10:25:57,707 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ 10:25:57,271 INFO @main [JournalStorageManager] Creating it
+ 10:25:57,276 INFO @main [JournalStorageManager] AIO loaded successfully
+ 10:25:57,689 INFO @main [MinaService] Registering:tcp://localhost:5400
+ 10:25:57,707 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
g.core.deployers.impl.SecurityDeployer at fe0fd9 with urlfile:/home/andy/project
s/jBossMessaging/build/messaging-2.0.0.alpha1/config/queues.xml
- 10:25:57,758 INFO @main [XmlDeployer] deploying topicjms.testTopic
- 10:25:57,761 INFO @main [XmlDeployer] deploying topicjms.securedTopic
- 10:25:57,761 INFO @main [XmlDeployer] deploying topicjms.testDurableTopic
- 10:25:57,762 INFO @main [XmlDeployer] deploying queuejms.testQueue
- 10:25:57,762 INFO @main [XmlDeployer] deploying queuejms.NoSuchQueue
- 10:25:57,763 INFO @main [XmlDeployer] deploying topicjms.NoSuchTopic
- 10:25:57,763 INFO @main [XmlDeployer] deploying queuetempjms.*
- 10:25:57,764 INFO @main [XmlDeployer] deploying topictempjms.*
- 10:25:57,764 INFO @main [XmlDeployer] deploying *
- 10:25:57,765 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ 10:25:57,758 INFO @main [XmlDeployer] deploying topicjms.testTopic
+ 10:25:57,761 INFO @main [XmlDeployer] deploying topicjms.securedTopic
+ 10:25:57,761 INFO @main [XmlDeployer] deploying topicjms.testDurableTopic
+ 10:25:57,762 INFO @main [XmlDeployer] deploying queuejms.testQueue
+ 10:25:57,762 INFO @main [XmlDeployer] deploying queuejms.NoSuchQueue
+ 10:25:57,763 INFO @main [XmlDeployer] deploying topicjms.NoSuchTopic
+ 10:25:57,763 INFO @main [XmlDeployer] deploying queuetempjms.*
+ 10:25:57,764 INFO @main [XmlDeployer] deploying topictempjms.*
+ 10:25:57,764 INFO @main [XmlDeployer] deploying *
+ 10:25:57,765 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
g.core.deployers.impl.QueueSettingsDeployer at 1220b36 with urlfile:/home/andy/p
rojects/jBossMessaging/build/messaging-2.0.0.alpha1/config/queues.xml
- 10:25:57,783 INFO @main [XmlDeployer] deploying queuejms.QueueWithOwnDLQAndE
+ 10:25:57,783 INFO @main [XmlDeployer] deploying queuejms.QueueWithOwnDLQAndE
xpiryQueue
- 10:25:57,784 INFO @main [XmlDeployer] deploying topicjms.TopicWithOwnDLQAndE
+ 10:25:57,784 INFO @main [XmlDeployer] deploying topicjms.TopicWithOwnDLQAndE
xpiryQueue
- 10:25:57,784 INFO @main [XmlDeployer] deploying queuejms.QueueWithOwnRedeliv
+ 10:25:57,784 INFO @main [XmlDeployer] deploying queuejms.QueueWithOwnRedeliv
eryDelay
- 10:25:57,784 INFO @main [XmlDeployer] deploying topicjms.TopicWithOwnRedeliv
+ 10:25:57,784 INFO @main [XmlDeployer] deploying topicjms.TopicWithOwnRedeliv
eryDelay
- 10:25:57,785 INFO @main [XmlDeployer] deploying queuejms.testDistributedQueu
+ 10:25:57,785 INFO @main [XmlDeployer] deploying queuejms.testDistributedQueu
e
- 10:25:57,785 INFO @main [XmlDeployer] deploying topicjms.testDistributedTopi
+ 10:25:57,785 INFO @main [XmlDeployer] deploying topicjms.testDistributedTopi
c
- 10:25:57,785 INFO @main [XmlDeployer] deploying queuejms.testPerfQueue
- 10:25:57,785 INFO @main [XmlDeployer] deploying *
- 10:26:02,824 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ 10:25:57,785 INFO @main [XmlDeployer] deploying queuejms.testPerfQueue
+ 10:25:57,785 INFO @main [XmlDeployer] deploying *
+ 10:26:02,824 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
g.core.deployers.impl.SecurityManagerDeployer at 1a1ff9 with urlfile:/home/andy/
projects/jBossMessaging/build/messaging-2.0.0.alpha1/config/jbm-security.xml
- 10:26:02,831 INFO @main [XmlDeployer] deploying guest
- 10:26:02,991 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ 10:26:02,831 INFO @main [XmlDeployer] deploying guest
+ 10:26:02,991 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
g.jms.server.impl.JMSServerDeployer at d6c07 with urlfile:/home/andy/projects/jB
ossMessaging/build/messaging-2.0.0.alpha1/config/jbm-jndi.xml
- 10:26:03,005 INFO @main [XmlDeployer] deploying DLQ
- 10:26:03,035 INFO @main [XmlDeployer] deploying ExpiryQueue
- 10:26:03,038 INFO @main [XmlDeployer] deploying testQueue
- 10:26:03,044 INFO @main [XmlDeployer] deploying testPerfQueue
- 10:26:03,046 INFO @main [XmlDeployer] deploying A
- 10:26:03,048 INFO @main [XmlDeployer] deploying B
- 10:26:03,050 INFO @main [XmlDeployer] deploying C
- 10:26:03,051 INFO @main [XmlDeployer] deploying D
- 10:26:03,072 INFO @main [XmlDeployer] deploying ex
- 10:26:03,075 INFO @main [XmlDeployer] deploying PrivateDLQ
- 10:26:03,077 INFO @main [XmlDeployer] deploying PrivateExpiryQueue
- 10:26:03,078 INFO @main [XmlDeployer] deploying QueueWithOwnDLQAndExpiryQueu
+ 10:26:03,005 INFO @main [XmlDeployer] deploying DLQ
+ 10:26:03,035 INFO @main [XmlDeployer] deploying ExpiryQueue
+ 10:26:03,038 INFO @main [XmlDeployer] deploying testQueue
+ 10:26:03,044 INFO @main [XmlDeployer] deploying testPerfQueue
+ 10:26:03,046 INFO @main [XmlDeployer] deploying A
+ 10:26:03,048 INFO @main [XmlDeployer] deploying B
+ 10:26:03,050 INFO @main [XmlDeployer] deploying C
+ 10:26:03,051 INFO @main [XmlDeployer] deploying D
+ 10:26:03,072 INFO @main [XmlDeployer] deploying ex
+ 10:26:03,075 INFO @main [XmlDeployer] deploying PrivateDLQ
+ 10:26:03,077 INFO @main [XmlDeployer] deploying PrivateExpiryQueue
+ 10:26:03,078 INFO @main [XmlDeployer] deploying QueueWithOwnDLQAndExpiryQueu
e
- 10:26:03,080 INFO @main [XmlDeployer] deploying QueueWithOwnRedeliveryDelay
- 10:26:03,081 INFO @main [XmlDeployer] deploying testDistributedQueue
- 10:26:03,083 INFO @main [XmlDeployer] deploying testTopic
- 10:26:03,086 INFO @main [XmlDeployer] deploying securedTopic
- 10:26:03,087 INFO @main [XmlDeployer] deploying testDurableTopic
- 10:26:03,088 INFO @main [XmlDeployer] deploying TopicWithOwnDLQAndExpiryQueu
+ 10:26:03,080 INFO @main [XmlDeployer] deploying QueueWithOwnRedeliveryDelay
+ 10:26:03,081 INFO @main [XmlDeployer] deploying testDistributedQueue
+ 10:26:03,083 INFO @main [XmlDeployer] deploying testTopic
+ 10:26:03,086 INFO @main [XmlDeployer] deploying securedTopic
+ 10:26:03,087 INFO @main [XmlDeployer] deploying testDurableTopic
+ 10:26:03,088 INFO @main [XmlDeployer] deploying TopicWithOwnDLQAndExpiryQueu
e
- 10:26:03,089 INFO @main [XmlDeployer] deploying TopicWithOwnRedeliveryDelay
- 10:26:03,090 INFO @main [XmlDeployer] deploying testDistributedTopic
- 10:26:03,091 INFO @main [XmlDeployer] deploying testConnectionFactory
- 10:26:03,091 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,101 INFO @main [XmlDeployer] deploying ConnectionFactory
- 10:26:03,101 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,102 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,103 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,103 WARN @main [JMSServerManagerImpl] Binding for java:/ConnectionF
+ 10:26:03,089 INFO @main [XmlDeployer] deploying TopicWithOwnRedeliveryDelay
+ 10:26:03,090 INFO @main [XmlDeployer] deploying testDistributedTopic
+ 10:26:03,091 INFO @main [XmlDeployer] deploying testConnectionFactory
+ 10:26:03,091 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,101 INFO @main [XmlDeployer] deploying ConnectionFactory
+ 10:26:03,101 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,102 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,103 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,103 WARN @main [JMSServerManagerImpl] Binding for java:/ConnectionF
actory already exists
- 10:26:03,103 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,104 WARN @main [JMSServerManagerImpl] Binding for java:/XAConnectio
+ 10:26:03,103 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,104 WARN @main [JMSServerManagerImpl] Binding for java:/XAConnectio
nFactory already exists
- 10:26:03,104 INFO @main [XmlDeployer] deploying ClusteredConnectionFactory
- 10:26:03,104 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,105 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,106 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,106 WARN @main [JMSServerManagerImpl] Binding for java:/ClusteredCo
+ 10:26:03,104 INFO @main [XmlDeployer] deploying ClusteredConnectionFactory
+ 10:26:03,104 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,105 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,106 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,106 WARN @main [JMSServerManagerImpl] Binding for java:/ClusteredCo
nnectionFactory already exists
- 10:26:03,106 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,106 WARN @main [JMSServerManagerImpl] Binding for java:/ClusteredXA
+ 10:26:03,106 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,106 WARN @main [JMSServerManagerImpl] Binding for java:/ClusteredXA
ConnectionFactory already exists
- 10:26:03,107 INFO @main [XmlDeployer] deploying MyExampleConnectionFactory
- 10:26:03,107 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,118 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,130 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,131 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
- 10:26:03,133 INFO @main [JBMBootstrapServer] JBM Server Started
+ 10:26:03,107 INFO @main [XmlDeployer] deploying MyExampleConnectionFactory
+ 10:26:03,107 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,118 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,130 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,131 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,133 INFO @main [JBMBootstrapServer] JBM Server Started
</programlisting>
<para>JBoss Messaging is now running. If any errors are seen, refer to the troubleshooting guide for help</para>
</section>
<section id="installation.jboss">
<title>Installing JBoss Messaging in JBoss AS 5</title>
- <para>At this point JBoss Messaging 2 Alpha is a technology preview and can only be run in standalone or embedded in your systems.</para>
+ <para>At this point JBoss Messaging 2 Alpha is a technology preview and we only support the standalone or embedded
+ versions.
+ </para>
</section>
</chapter>
\ No newline at end of file
Modified: trunk/examples/jms/config/jndi.properties
===================================================================
--- trunk/examples/jms/config/jndi.properties 2008-05-29 14:52:18 UTC (rev 4339)
+++ trunk/examples/jms/config/jndi.properties 2008-05-29 15:18:54 UTC (rev 4340)
@@ -1,3 +1,3 @@
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
-java.naming.provider.url=jnp://192.168.1.13:1099
+java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
Modified: trunk/src/config/jbm-jndi.xml
===================================================================
--- trunk/src/config/jbm-jndi.xml 2008-05-29 14:52:18 UTC (rev 4339)
+++ trunk/src/config/jbm-jndi.xml 2008-05-29 15:18:54 UTC (rev 4340)
@@ -27,25 +27,23 @@
<entry name="java:/connectionfactories/acme/connection_factory"/>
<!-- You can specify the default Client ID to use for connections created using this factory -->
<client-id>MyClientID</client-id>
- <!-- PrefetchSize determines the maximum number of messages the client consumer will buffer locally -->
- <prefetch-size>150</prefetch-size>
<!-- The batch size to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode -->
- <dups-ok-batch-size>5000</dups-ok-batch-size>
- <!-- Does this connection factory support automatic failover? -->
- <supports-failover>false</supports-failover>
- <!-- Does this connection factory support automatic client side load balancing? -->
- <supports-load-balancing>false</supports-load-balancing>
- <!-- The class name of the factory used to create the load balancing policy to use on the client side -->
- <load-balancing-factory>org.jboss.messaging.jms.client.plugin.RoundRobinLoadBalancingFactory</load-balancing-factory>
- <!-- Whether we should be strict TCK compliant, i.e. how we deal with foreign messages, defaults to false-->
- <strict-tck>true</strict-tck>
-
+ <dups-ok-batch-size>5000</dups-ok-batch-size>-size>
<!-- This is the window size in number of messages to use when using producer window based flow control -->
<producer-window-size>1000</producer-window-size>
-
<!-- This is the maximum producer send rate that will be applied when using rate based producer flow control -->
<producer-max-rate>100</producer-max-rate>
-
+ <!-- This is the window size in number of messages to use when using consumer window based flow control -->
+ <consumer-window-size>1000</consumer-window-size>
+ <!-- This is the maximum producer send rate that will be applied when using rate based consumer flow control -->
+ <consumer-max-rate>5000</consumer-max-rate>
+ <!--Whether or not we use a blocking call when acknowledging a message-->
+ <block-on-acknowledge>false</block-on-acknowledge>
+ <!--Whether we send non persistent messages synchronously-->
+ <send-np-messages-synchronously>true</send-np-messages-synchronously>
+ <!--Whether we send persistent messages synchronously-->
+ <send-p-messages-synchronously>true</send-p-messages-synchronously>
+
</connection-factory>
<queue name="DLQ">
More information about the jboss-cvs-commits
mailing list