[jboss-cvs] JBoss Messaging SVN: r3143 - trunk/docs/userguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Sep 27 11:41:13 EDT 2007
Author: ataylor
Date: 2007-09-27 11:41:13 -0400 (Thu, 27 Sep 2007)
New Revision: 3143
Modified:
trunk/docs/userguide/en/modules/about.xml
trunk/docs/userguide/en/modules/bridge.xml
trunk/docs/userguide/en/modules/c_configuration.xml
trunk/docs/userguide/en/modules/configuration.xml
trunk/docs/userguide/en/modules/installation.xml
trunk/docs/userguide/en/modules/recovery_config.xml
Log:
http://jira.jboss.com/jira/browse/JBMESSAGING-1044 - tidied up docs
Modified: trunk/docs/userguide/en/modules/about.xml
===================================================================
--- trunk/docs/userguide/en/modules/about.xml 2007-09-26 19:23:42 UTC (rev 3142)
+++ trunk/docs/userguide/en/modules/about.xml 2007-09-27 15:41:13 UTC (rev 3143)
@@ -66,6 +66,6 @@
<para>Messaging support team: Jay Howell, David Boeren, Mike Clark, Tyronne Wickramarathne
</para>
- <para>Other thanks to Mark LIttle and Pete Bennett</para>
+ <para>Other thanks to Mark Little and Pete Bennett</para>
</chapter>
Modified: trunk/docs/userguide/en/modules/bridge.xml
===================================================================
--- trunk/docs/userguide/en/modules/bridge.xml 2007-09-26 19:23:42 UTC (rev 3142)
+++ trunk/docs/userguide/en/modules/bridge.xml 2007-09-27 15:41:13 UTC (rev 3143)
@@ -5,7 +5,7 @@
<section id="bridge.overview">
<title>Message bridge overview</title>
- <para>JBoss Messaging includes a fully functional message bridge</para>
+ <para>JBoss Messaging includes a fully functional message bridge.</para>
<para>The function of the bridge is to consume messages from a source queue or topic, and send them to target
queue or topic, typically on a different server.
@@ -134,10 +134,12 @@
xmbean-dd="xmdesc/Bridge-xmbean.xml">
<!-- The JMS provider loader that is used to lookup the source destination -->
- <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
+ <depends optional-attribute-name="SourceProviderLoader">
+ jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
<!-- The JMS provider loader that is used to lookup the target destination -->
- <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
+ <depends optional-attribute-name="TargetProviderLoader">
+ jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
<!-- The JNDI lookup for the source destination -->
<attribute name="SourceDestinationLookup">/queue/A</attribute>
@@ -171,10 +173,12 @@
<attribute name="Selector">specify jms selector here</attribute>
-->
- <!-- The maximum number of messages to consume from the source before sending to the target -->
+ <!-- The maximum number of messages to consume from the source
+ before sending to the target -->
<attribute name="MaxBatchSize">5</attribute>
- <!-- The maximum time to wait (in ms) before sending a batch to the target even if MaxBatchSize is not exceeded.
+ <!-- The maximum time to wait (in ms) before sending a batch to the target
+ even if MaxBatchSize is not exceeded.
-1 means wait forever -->
<attribute name="MaxBatchTime">-1</attribute>
@@ -186,15 +190,17 @@
<attribute name="ClientID">myClientID</attribute>
-->
- <!-- The number of ms to wait between connection retrues in the event connections to source or target fail -->
+ <!-- The number of ms to wait between connection retrues in the event connections
+ to source or target fail -->
<attribute name="FailureRetryInterval">5000</attribute>
- <!-- The maximum number of connection retries to make in case of failure, before giving up
- -1 means try forever-->
+ <!-- The maximum number of connection retries to make in case of failure,
+ before giving up -1 means try forever-->
<attribute name="MaxRetries">-1</attribute>
- <!-- If true then the message id of the message before bridging will be added as a header to the message so it is available
- to the receiver. Can then be sent as correlation id to correlate in a distributed request-response -->
+ <!-- If true then the message id of the message before bridging will be added
+ as a header to the message so it is available to the receiver. Can then be
+ sent as correlation id to correlate in a distributed request-response -->
<attribute name="AddMessageIDInHeader">false</attribute>
</mbean>
@@ -253,7 +259,13 @@
<section id="bridge.configuration.qualityofservicemode">
<title>QualityOfServiceMode</title>
<para>This integer represents the desired quality of service mode</para>
- <para>Possible values are QOS_AT_MOST_ONCE = 0, QOS_DUPLICATES_OK = 1, QOS_ONCE_AND_ONLY_ONCE = 2</para>
+ <para>Possible values are:
+ <itemizedlist>
+ <listitem>QOS_AT_MOST_ONCE = 0</listitem>
+ <listitem>QOS_DUPLICATES_OK = 1</listitem>
+ <listitem>QOS_ONCE_AND_ONLY_ONCE = 2</listitem>
+ </itemizedlist>
+ </para>
<para>Please see <xref linkend="bridge.overview"/> for an explanation of what these mean.</para>
</section>
Modified: trunk/docs/userguide/en/modules/c_configuration.xml
===================================================================
--- trunk/docs/userguide/en/modules/c_configuration.xml 2007-09-26 19:23:42 UTC (rev 3142)
+++ trunk/docs/userguide/en/modules/c_configuration.xml 2007-09-27 15:41:13 UTC (rev 3143)
@@ -1,9 +1,9 @@
-<chapter id="c_configuration">
-
- <title>JBoss Messaging Clustering Configuration</title>
-
- <para>
- JBoss Messaging clustering should work out of the box in most cases with no configuration changes. It is however crucial that every node in the cluster is assigned a unique server id, as specified in the installation guide.
+<chapter id="c_configuration">
+
+ <title>JBoss Messaging Clustering Configuration</title>
+
+ <para>
+ JBoss Messaging clustering should work out of the box in most cases with no configuration changes. It is however crucial that every node in the cluster is assigned a unique server id, as specified in the installation guide.
</para>
<para>JBoss Messaging clusters JMS queues and topics transparently across the cluster. Messages sent to a distributed queue or topic on one node are consumable on other nodes. To designate that a particular destination is clustered simply set the clustered attribute in the destination deployment descriptor to true.
@@ -19,13 +19,13 @@
<para>JBoss Messaging also supports clustered temporary topics and queues. All temporary topics and queues will be clustered if the post office is clustered
</para>
- <para>If you do want your nodes to participate in a cluster, or only have one non clustered server you can set the clustered attribute on the postoffice to false
+ <para>If you don't want your nodes to participate in a cluster, or only have one non clustered server you can set the clustered attribute on the postoffice to false
</para>
<para>If you wish to apply strict JMS ordering to messages, such that a particular JMS consumer consumes messages in the same order as they were produced by a particular producer, you can set the DefaultPreserveOrdering attribute in the server peer to true. By default this is false. The side-effect of setting this to true is that messages cannot be distributed as freely around the cluster
</para>
<para>When pulling reliable messages from one node to another, by default JBoss Messaging uses an XA transaction to ensure that message was removed from one node and added to another transactionally. Using XA transactions is a fairly heavyweight operation. If you are willing to to relax the reliability guarantee somewhat in order to gain some performance then you can set the attribute UseXAForMessagePull in server peer to false. By default it is true
- </para>
-
+ </para>
+
</chapter>
Modified: trunk/docs/userguide/en/modules/configuration.xml
===================================================================
--- trunk/docs/userguide/en/modules/configuration.xml 2007-09-26 19:23:42 UTC (rev 3142)
+++ trunk/docs/userguide/en/modules/configuration.xml 2007-09-27 15:41:13 UTC (rev 3143)
@@ -30,7 +30,7 @@
<para>
The AOP client-side and server-side interceptor stacks are configured in
<filename>aop-messaging-client.xml</filename> and <filename>aop-messaging-server.xml</filename>.
- Normally you will not want to change them, but you can some of the interceptors can be removed
+ Normally you will not want to change them, but some of the interceptors can be removed
to give a small performance increase, if you don't need them. Be very careful you have considered the security implications before removing the
security interceptor.
</para>
@@ -53,15 +53,19 @@
name="jboss.messaging:service=ServerPeer"
xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
- <!-- The unique id of the server peer - in a cluster each node MUST have a unique value - must be an integer -->
+ <!-- The unique id of the server peer
+ - in a cluster each node MUST have a unique value
+ - must be an integer -->
<attribute name="ServerPeerID">0</attribute>
- <!-- The default JNDI context to use for queues when they are deployed without specifying one -->
+ <!-- The default JNDI context to use for queues
+ when they are deployed without specifying one -->
<attribute name="DefaultQueueJNDIContext">/queue</attribute>
- <!-- The default JNDI context to use for topics when they are deployed without specifying one -->
+ <!-- The default JNDI context to use for topics
+ when they are deployed without specifying one -->
<attribute name="DefaultTopicJNDIContext">/topic</attribute>
@@ -71,7 +75,8 @@
<attribute name="SecurityDomain">java:/jaas/messaging</attribute>
- <!-- The default security configuration to apply to destinations - this can be overridden on a per destination basis -->
+ <!-- The default security configuration to apply to destinations
+ - this can be overridden on a per destination basis -->
<attribute name="DefaultSecurityConfig">
<security>
@@ -82,32 +87,40 @@
<!-- The default Dead Letter Queue (DLQ) to use for destinations.
This can be overridden on a per destinatin basis -->
- <attribute name="DefaultDLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>
+ <attribute name="DefaultDLQ">
+ jboss.messaging.destination:service=Queue,name=DLQ<
+ /attribute>
- <!-- The default maximum number of times to attempt delivery of a message before sending to the DLQ (if configured).
+ <!-- The default maximum number of times to attempt delivery of a message
+ before sending to the DLQ (if configured).
This can be overridden on a per destinatin basis -->
<attribute name="DefaultMaxDeliveryAttempts">10</attribute>
- <!-- The default Expiry Queue to use for destinations. This can be overridden on a per destinatin basis -->
+ <!-- The default Expiry Queue to use for destinations.
+ This can be overridden on a per destinatin basis -->
- <attribute name="DefaultExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
+ <attribute name="DefaultExpiryQueue">
+ jboss.messaging.destination:service=Queue,name=ExpiryQueue
+ </attribute>
- <!-- The default redelivery delay to impose. This can be overridden on a per destination basis -->
+ <!-- The default redelivery delay to impose.
+ This can be overridden on a per destination basis -->
<attribute name="DefaultRedeliveryDelay">0</attribute>
- <!-- The periodicity of the message counter manager enquiring on queues for statistics -->
+ <!-- The periodicity of the message counter manager enquiring on queues
+ for statistics -->
<attribute name="MessageCounterSamplePeriod">5000</attribute>
- <!-- The maximum amount of time for a client to wait for failover to start on the server side after
- it has detected failure -->
+ <!-- The maximum amount of time for a client to wait for failover
+ to start on the server side after it has detected failure -->
<attribute name="FailoverStartTimeout">60000</attribute>
- <!-- The maximum amount of time for a client to wait for failover to complete on the server side after
- it has detected failure -->
+ <!-- The maximum amount of time for a client to wait for failover to complete
+ on the server side after it has detected failure -->
<attribute name="FailoverCompleteTimeout">300000</attribute>
@@ -115,20 +128,24 @@
<attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>
- <!-- The name of the connection factory to use for creating connections between nodes to pull messages -->
+ <!-- The name of the connection factory to use for creating connections between nodes
+ to pull messages -->
- <attribute name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</attribute>
+ <attribute name="ClusterPullConnectionFactoryName">
+ jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
+ </attribute>
<!-- Use XA when pulling persistent messages from a remote node to this one. -->
<attribute name="UseXAForMessagePull">true</attribute>
- <!-- When redistributing messages in the cluster. Do we need to preserve the order of messages received
- by a particular consumer from a particular producer? -->
+ <!-- When redistributing messages in the cluster. Do we need to preserve the order of
+ messages received by a particular consumer from a particular producer? -->
<attribute name="DefaultPreserveOrdering">false</attribute>
- <!-- Max. time to hold previously delivered messages back waiting for clients to reconnect after failover -->
+ <!-- Max. time to hold previously delivered messages back waiting for clients
+ to reconnect after failover -->
<attribute name="RecoverDeliveriesTimeout">300000</attribute>
@@ -137,9 +154,13 @@
<attribute name="SuckerPassword"></attribute>
-->
- <depends optional-attribute-name="PersistenceManager">jboss.messaging:service=PersistenceManager</depends>
+ <depends optional-attribute-name="PersistenceManager">
+ jboss.messaging:service=PersistenceManager
+ </depends>
- <depends optional-attribute-name="JMSUserManager">jboss.messaging:service=JMSUserManager</depends>
+ <depends optional-attribute-name="JMSUserManager">
+ jboss.messaging:service=JMSUserManager
+ </depends>
<depends>jboss.messaging:service=Connector,transport=bisocket</depends>
@@ -151,7 +172,7 @@
<title>ServerPeer attributes</title>
<para>
- We now discuss the MBean attributes of the ServerPeer MBean
+ We now discuss the MBean attributes of the ServerPeer MBean.
</para>
<section id="conf.serverpeer.attributes.serverpeerid">
@@ -255,9 +276,9 @@
The default for the maximum number of times delivery of a message will be attempted before sending the message to the DLQ, if configured.
</para>
<para>
- The default value is <literal>10</literal >
+ The default value is <literal>10</literal >.
</para>
- <para>This value can also be overridden on a per destination basis</para>
+ <para>This value can also be overridden on a per destination basis.</para>
</section>
<section id="conf.serverpeer.attributes.defaultexpiryqueue">
@@ -286,7 +307,7 @@
The default value is <literal>0</literal> which means there will be no delay.
</para>
<para>Change this if your application could benefit with a delay before redelivery.
- This value can also be overridden on a per destination basis
+ This value can also be overridden on a per destination basis.
</para>
</section>
@@ -297,7 +318,7 @@
Periodically the server will query each queue to gets its statistics. This is the period.
</para>
<para>
- The default value is <literal>10000</literal> milliseconds
+ The default value is <literal>10000</literal> milliseconds.
</para>
</section>
@@ -308,7 +329,7 @@
The maximum number of milliseconds the client will wait for failover to start on the server side when a problem is detected.
</para>
<para>
- The default value is <literal>60000</literal> (one minute)
+ The default value is <literal>60000</literal> (one minute).
</para>
</section>
@@ -320,7 +341,7 @@
The maximum number of milliseconds the client will wait for failover to complete on the server side after it has started.
</para>
<para>
- The default value is <literal>300000</literal> (five minutes)
+ The default value is <literal>300000</literal> (five minutes).
</para>
</section>
@@ -331,7 +352,7 @@
<para>
JBoss Messaging provides a message counter history which shows the number of messages arriving on each queue of a certain number of
days. This attribute represents the maxiumum number of days for which to store message counter history. It can be overridden on a per
- destination basis
+ destination basis.
</para>
</section>
@@ -339,7 +360,7 @@
<title>ClusterPullConnectionFactory</title>
<para>
- The name of the connection factory to use for pulling messages between nodes. You will not normally need to change this
+ The name of the connection factory to use for pulling messages between nodes. You will not normally need to change this.
</para>
</section>
@@ -347,7 +368,7 @@
<title>UseXAForMessagePull</title>
<para>
- If true, then move a reliable message from one node to another in an XA transaction. Relaxing this gives better performance at the expense of some reliability. See the cluster configurations section for more details. Default is true
+ If true, then move a reliable message from one node to another in an XA transaction. Relaxing this gives better performance at the expense of some reliability. See the cluster configurations section for more details. Default is true.
</para>
</section>
@@ -375,7 +396,7 @@
These connections are made with the user name of a special reserved user.
The password used by that user is specified by this parameter.
<warning>This must be specified at install time, or the default password will be used. Any one who then knows
- the default password will be able to gain access to any destinations on the server</warning>
+ the default password will be able to gain access to any destinations on the server.</warning>
</para>
</section>
@@ -433,7 +454,7 @@
<section id="conf.serverpeer.operations">
<title>
- We now discuss the MBean operations of the ServerPeer MBean
+ We now discuss the MBean operations of the ServerPeer MBean.
</title>
<section id="conf.serverpeer.operations.deployQueue">
@@ -445,16 +466,16 @@
<para>There are two overloaded versions of this operation</para>
- <para>If the queue already exists but is undeployed it is deployed. Otherwise it is created and deployed</para>
+ <para>If the queue already exists but is undeployed it is deployed. Otherwise it is created and deployed.</para>
<para>The <literal>name</literal> parameter represents the name of the destination to deploy.</para>
<para>The <literal>jndiName</literal> parameter (optional) represents the full jndi name where to bind the destination.
- If this is not specified then the destination will be bound in <DefaultQueueJNDIContext>/<name>
+ If this is not specified then the destination will be bound in <DefaultQueueJNDIContext>/<name>.
</para>
<para>The first version of this operation deploys the destination with the default paging parameters. The second overloaded version deploys
the destination with the specified paging parameters. See the section on configuring destinations for a discussion of what the
- paging parameters mean</para>
+ paging parameters mean.</para>
</section>
@@ -467,7 +488,7 @@
<para>The queue is undeployed but is NOT removed from persistent storage.</para>
- <para>This operation returns <literal>true</literal> if the queue was successfull undeployed. otherwise it returns <literal>false</literal></para>
+ <para>This operation returns <literal>true</literal> if the queue was successfull undeployed. otherwise it returns <literal>false</literal>.</para>
</section>
@@ -478,12 +499,12 @@
This operation lets you programmatically destroy a queue.
</para>
- <para>The queue is undeployed and then all its data is destroyed from the database</para>
+ <para>The queue is undeployed and then all its data is destroyed from the database.</para>
- <warning>Be careful when using this method since it will delete all data for the queue</warning>
+ <warning>Be careful when using this method since it will delete all data for the queue.</warning>
<para>This operation returns <literal>true</literal> if the
- queue was successfully destroyed. otherwise it returns <literal>false</literal></para>
+ queue was successfully destroyed. otherwise it returns <literal>false</literal>.</para>
</section>
@@ -495,17 +516,17 @@
This operation lets you programmatically deploy a topic.
</para>
- <para>There are two overloaded versions of this operation</para>
+ <para>There are two overloaded versions of this operation.</para>
- <para>If the topic already exists but is undeployed it is deployed. Otherwise it is created and deployed</para>
+ <para>If the topic already exists but is undeployed it is deployed. Otherwise it is created and deployed.</para>
<para>The <literal>name</literal> parameter represents the name of the destination to deploy.</para>
<para>The <literal>jndiName</literal> parameter (optional) represents the full jndi name where to bind the destination. If this is not specified
- then the destination will be bound in <DefaultTopicJNDIContext>/<name></para>
+ then the destination will be bound in <DefaultTopicJNDIContext>/<name>.</para>
<para>The first version of this operation deploys the destination with the default paging parameters. The second overloaded version deploys
the destination with the specified paging parameters. See the section on configuring destinations for a discussion of what the
- paging parameters mean</para>
+ paging parameters mean.</para>
</section>
@@ -518,7 +539,7 @@
<para>The queue is undeployed but is NOT removed from persistent storage.</para>
- <para>This operation returns <literal>true</literal> if the topic was successfully undeployed. otherwise it returns <literal>false</literal></para>
+ <para>This operation returns <literal>true</literal> if the topic was successfully undeployed. otherwise it returns <literal>false</literal>.</para>
</section>
@@ -529,11 +550,11 @@
This operation lets you programmatically destroy a topic.
</para>
- <para>The topic is undeployed and then all its data is destroyed from the database</para>
+ <para>The topic is undeployed and then all its data is destroyed from the database.</para>
- <warning>Be careful when using this method since it will delete all data for the topic</warning>
+ <warning>Be careful when using this method since it will delete all data for the topic.</warning>
- <para>This operation returns <literal>true</literal> if the topic was successfully destroyed. otherwise it returns <literal>false</literal></para>
+ <para>This operation returns <literal>true</literal> if the topic was successfully destroyed. otherwise it returns <literal>false</literal>.</para>
</section>
@@ -609,7 +630,7 @@
The Persistence Manager is used to handle the message-related persistence.
The Post Office handles binding related persistence.
The JMS User manager handles user related persistence
- The configuration for all these MBeans is handled in the <filename>xxx-persistence-service.xml</filename> file
+ The configuration for all these MBeans is handled in the <filename>xxx-persistence-service.xml</filename> file.
</para>
<para>
@@ -648,11 +669,11 @@
queue - the JMS queue. When sending a message with an address that repesents a JMS topic name, the post office will route this to a set of
queues - one for each JMS subscription.</para>
- <para>The post office also handles the persistence for the mapping of addresses</para>
+ <para>The post office also handles the persistence for the mapping of addresses.</para>
<para>JBoss messaging are also cluster aware. In a cluster they will automatically route and pull messages between them in order to provide fully distributed JMS queues and topics.</para>
- <para>The post office configuration is found in the xxx-persistence-service.xml file (where xxx is the name of your database)
+ <para>The post office configuration is found in the xxx-persistence-service.xml file (where xxx is the name of your database).
</para>
<para>Here is an example of a post office configuration:</para>
@@ -662,11 +683,15 @@
name="jboss.messaging:service=PostOffice"
xmbean-dd="xmdesc/MessagingPostOffice-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
- <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
+ <depends optional-attribute-name="TransactionManager">
+ jboss:service=TransactionManager
+ </depends>
<!-- The name of the post office -->
@@ -681,18 +706,28 @@
<attribute name="CreateTablesOnStartup">true</attribute>
<attribute name="SqlProperties"><![CDATA[
-CREATE_POSTOFFICE_TABLE=CREATE TABLE JBM_POSTOFFICE (POSTOFFICE_NAME VARCHAR(255), NODE_ID INTEGER, QUEUE_NAME VARCHAR(255), COND VARCHAR(1023), SELECTOR VARCHAR(1023), CHANNEL_ID BIGINT, CLUSTERED CHAR(1), ALL_NODES CHAR(1), PRIMARY KEY(POSTOFFICE_NAME, NODE_ID, QUEUE_NAME)) ENGINE = INNODB
-INSERT_BINDING=INSERT INTO JBM_POSTOFFICE (POSTOFFICE_NAME, NODE_ID, QUEUE_NAME, COND, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
-DELETE_BINDING=DELETE FROM JBM_POSTOFFICE WHERE POSTOFFICE_NAME=? AND NODE_ID=? AND QUEUE_NAME=?
-LOAD_BINDINGS=SELECT QUEUE_NAME, COND, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES FROM JBM_POSTOFFICE WHERE POSTOFFICE_NAME=? AND NODE_ID=?
+CREATE_POSTOFFICE_TABLE=CREATE TABLE JBM_POSTOFFICE (POSTOFFICE_NAME VARCHAR(255),
+ NODE_ID INTEGER, QUEUE_NAME VARCHAR(255), COND VARCHAR(1023),
+ SELECTOR VARCHAR(1023), CHANNEL_ID BIGINT, CLUSTERED CHAR(1),
+ ALL_NODES CHAR(1), PRIMARY KEY(POSTOFFICE_NAME, NODE_ID, QUEUE_NAME))
+ ENGINE = INNODB
+INSERT_BINDING=INSERT INTO JBM_POSTOFFICE (POSTOFFICE_NAME, NODE_ID, QUEUE_NAME,
+ COND, SELECTOR, CHANNEL_ID, CLUSTERED, ALL_NODES)
+ VALUES (?, ?, ?, ?, ?, ?, ?, ?)
+DELETE_BINDING=DELETE FROM JBM_POSTOFFICE WHERE POSTOFFICE_NAME=? AND NODE_ID=?
+ AND QUEUE_NAME=? LOAD_BINDINGS=SELECT QUEUE_NAME, COND, SELECTOR,
+ CHANNEL_ID, CLUSTERED, ALL_NODES FROM JBM_POSTOFFICE WHERE POSTOFFICE_NAME=?
+ AND NODE_ID=?
]]></attribute>
- <!-- This post office is clustered. If you don't want a clustered post office then set to false -->
+ <!-- This post office is clustered. If you don't want a clustered post office
+ then set to false -->
<attribute name="Clustered">true</attribute>
- <!-- All the remaining properties only have to be specified if the post office is clustered.
- You can safely comment them out if your post office is non clustered -->
+ <!-- All the remaining properties only have to be specified if the post office
+ is clustered. You can safely comment them out if your post office is
+ non clustered -->
<!-- The JGroups group name that the post office will use -->
@@ -702,7 +737,8 @@
<attribute name="StateTimeout">5000</attribute>
- <!-- Max time to wait for a synchronous call to node members using the MessageDispatcher -->
+ <!-- Max time to wait for a synchronous call to node members using
+ the MessageDispatcher -->
<attribute name="CastTimeout">50000</attribute>
@@ -710,53 +746,143 @@
<attribute name="ChannelFactoryName">jgroups.mux:name=Multiplexer</attribute>
<attribute name="ControlChannelName">udp-sync</attribute>
<attribute name="DataChannelName">udp</attribute>
- <attribute name="ChannelPartitionName">${jboss.partition.name:DefaultPartition}-JMS</attribute>
+ <attribute name="ChannelPartitionName">
+ ${jboss.partition.name:DefaultPartition}-JMS
+ </attribute>
-->
- <!-- JGroups stack configuration for the data channel - used when casting messages across the cluster -->
+ <!-- JGroups stack configuration for the data channel - used when casting
+ messages across the cluster -->
<attribute name="DataChannelConfig">
<config>
- <UDP mcast_recv_buf_size="500000" down_thread="false" ip_mcast="true" mcast_send_buf_size="32000"
- mcast_port="45567" ucast_recv_buf_size="500000" use_incoming_packet_handler="false"
- mcast_addr="228.8.8.8" use_outgoing_packet_handler="true" loopback="true" ucast_send_buf_size="32000" ip_ttl="32"/>
- <AUTOCONF down_thread="false" up_thread="false"/>
- <PING timeout="2000" down_thread="false" num_initial_members="3" up_thread="false"/>
- <MERGE2 max_interval="10000" down_thread="false" min_interval="5000" up_thread="false"/>
- <FD_SOCK down_thread="false" up_thread="false"/>
- <FD timeout="20000" max_tries="3" down_thread="false" up_thread="false" shun="true"/>
- <VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false"/>
- <pbcast.NAKACK max_xmit_size="8192" down_thread="false" use_mcast_xmit="true" gc_lag="50" up_thread="false"
- retransmit_timeout="100,200,600,1200,2400,4800"/>
- <UNICAST timeout="1200,2400,3600" down_thread="false" up_thread="false"/>
- <pbcast.STABLE stability_delay="1000" desired_avg_gossip="20000" down_thread="false" max_bytes="0" up_thread="false"/>
- <FRAG frag_size="8192" down_thread="false" up_thread="false"/>
- <VIEW_SYNC avg_send_interval="60000" down_thread="false" up_thread="false" />
- <pbcast.GMS print_local_addr="true" join_timeout="3000" down_thread="false" join_retry_timeout="2000" up_thread="false" shun="true"/>
+ <UDP mcast_recv_buf_size="500000"
+ down_thread="false"
+ ip_mcast="true"
+ mcast_send_buf_size="32000"
+ mcast_port="45567"
+ ucast_recv_buf_size="500000"
+ use_incoming_packet_handler="false"
+ mcast_addr="228.8.8.8"
+ use_outgoing_packet_handler="true"
+ loopback="true"
+ ucast_send_buf_size="32000"
+ ip_ttl="32"/>
+ <AUTOCONF down_thread="false"
+ up_thread="false"/>
+ <PING timeout="2000"
+ down_thread="false"
+ num_initial_members="3"
+ up_thread="false"/>
+ <MERGE2 max_interval="10000"
+ down_thread="false"
+ min_interval="5000"
+ up_thread="false"/>
+ <FD_SOCK down_thread="false"
+ up_thread="false"/>
+ <FD timeout="20000"
+ max_tries="3"
+ down_thread="false"
+ up_thread="false"
+ shun="true"/>
+ <VERIFY_SUSPECT timeout="1500"
+ down_thread="false"
+ up_thread="false"/>
+ <pbcast.NAKACK max_xmit_size="8192"
+ down_thread="false"
+ use_mcast_xmit="true"
+ gc_lag="50"
+ up_thread="false"
+ retransmit_timeout="100,200,600,1200,2400,4800"/>
+ <UNICAST timeout="1200,2400,3600"
+ down_thread="false"
+ up_thread="false"/>
+ <pbcast.STABLE stability_delay="1000"
+ desired_avg_gossip="20000"
+ down_thread="false"
+ max_bytes="0"
+ up_thread="false"/>
+ <FRAG frag_size="8192"
+ down_thread="false"
+ up_thread="false"/>
+ <VIEW_SYNC avg_send_interval="60000"
+ down_thread="false"
+ up_thread="false" />
+ <pbcast.GMS print_local_addr="true"
+ join_timeout="3000"
+ down_thread="false"
+ join_retry_timeout="2000"
+ up_thread="false"
+ shun="true"/>
</config>
</attribute>
- <!-- JGroups stack configuration to use for the control channel - used for bind/unbind requests amongst others -->
+ <!-- JGroups stack configuration to use for the control channel -
+ used for bind/unbind requests amongst others -->
<attribute name="ControlChannelConfig">
<config>
- <UDP mcast_recv_buf_size="500000" down_thread="false" ip_mcast="true" mcast_send_buf_size="32000"
- mcast_port="45568" ucast_recv_buf_size="500000" use_incoming_packet_handler="false"
- mcast_addr="228.8.8.8" use_outgoing_packet_handler="true" loopback="true" ucast_send_buf_size="32000" ip_ttl="32"/>
- <AUTOCONF down_thread="false" up_thread="false"/>
- <PING timeout="2000" down_thread="false" num_initial_members="3" up_thread="false"/>
- <MERGE2 max_interval="10000" down_thread="false" min_interval="5000" up_thread="false"/>
- <FD_SOCK down_thread="false" up_thread="false"/>
- <FD timeout="20000" max_tries="3" down_thread="false" up_thread="false" shun="true"/>
- <VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false"/>
- <pbcast.NAKACK max_xmit_size="8192" down_thread="false" use_mcast_xmit="true" gc_lag="50" up_thread="false"
- retransmit_timeout="100,200,600,1200,2400,4800"/>
- <UNICAST timeout="1200,2400,3600" down_thread="false" up_thread="false"/>
- <pbcast.STABLE stability_delay="1000" desired_avg_gossip="20000" down_thread="false" max_bytes="0" up_thread="false"/>
- <FRAG frag_size="8192" down_thread="false" up_thread="false"/>
- <VIEW_SYNC avg_send_interval="60000" down_thread="false" up_thread="false" />
- <pbcast.GMS print_local_addr="true" join_timeout="3000" down_thread="false" join_retry_timeout="2000" up_thread="false" shun="true"/>
- <pbcast.STATE_TRANSFER down_thread="false" up_thread="false"/>
+ <UDP
+ mcast_recv_buf_size="500000"
+ down_thread="false"
+ ip_mcast="true"
+ mcast_send_buf_size="32000"
+ mcast_port="45568"
+ ucast_recv_buf_size="500000"
+ use_incoming_packet_handler="false"
+ mcast_addr="228.8.8.8"
+ use_outgoing_packet_handler="true"
+ loopback="true"
+ ucast_send_buf_size="32000"
+ ip_ttl="32"/>
+ <AUTOCONF down_thread="false"
+ up_thread="false"/>
+ <PING timeout="2000"
+ down_thread="false"
+ num_initial_members="3"
+ up_thread="false"/>
+ <MERGE2 max_interval="10000"
+ down_thread="false"
+ min_interval="5000"
+ up_thread="false"/>
+ <FD_SOCK down_thread="false"
+ up_thread="false"/>
+ <FD timeout="20000"
+ max_tries="3"
+ down_thread="false"
+ up_thread="false"
+ shun="true"/>
+ <VERIFY_SUSPECT timeout="1500"
+ down_thread="false"
+ up_thread="false"/>
+ <pbcast.NAKACK max_xmit_size="8192"
+ down_thread="false"
+ use_mcast_xmit="true"
+ gc_lag="50"
+ up_thread="false"
+ retransmit_timeout="100,200,600,1200,2400,4800"/>
+ <UNICAST timeout="1200,2400,3600"
+ down_thread="false"
+ up_thread="false"/>
+ <pbcast.STABLE stability_delay="1000"
+ desired_avg_gossip="20000"
+ down_thread="false"
+ max_bytes="0"
+ up_thread="false"/>
+ <FRAG frag_size="8192"
+ down_thread="false"
+ up_thread="false"/>
+ <VIEW_SYNC avg_send_interval="60000"
+ down_thread="false"
+ up_thread="false" />
+ <pbcast.GMS print_local_addr="true"
+ join_timeout="3000"
+ down_thread="false"
+ join_retry_timeout="2000"
+ up_thread="false"
+ shun="true"/>
+ <pbcast.STATE_TRANSFER down_thread="false"
+ up_thread="false"/>
</config>
</attribute>
</mbean>
@@ -768,7 +894,7 @@
<section id="conf.postoffice.attributes.datasource">
<title>DataSource</title>
- <para>The datasource the postoffice should use for persisting its mapping data</para>
+ <para>The datasource the postoffice should use for persisting its mapping data.</para>
</section>
<section id="conf.postoffice.attributes.sqlproperties">
@@ -799,7 +925,7 @@
<title>PostOfficeName</title>
<para>
- The name of the post office
+ The name of the post office.
</para>
</section>
@@ -807,7 +933,7 @@
<title>NodeIDView</title>
<para>
- This returns set containing the node ids of all the nodes in the cluster
+ This returns set containing the node ids of all the nodes in the cluster.
</para>
</section>
@@ -832,16 +958,16 @@
<title>StateTimeout</title>
<para>The maximum time to wait when waiting for the group state to arrive when a node joins a pre-existing cluster.
</para>
- <para>The default value is <literal>5000</literal> milliseconds
+ <para>The default value is <literal>5000</literal> milliseconds.
</para>
</section>
<section id="conf.postoffice.attributes.casttimeout">
<title>CastTimeout</title>
<para>
- The maximum time to wait for a reply casting message synchronously
+ The maximum time to wait for a reply casting message synchronously.
</para>
- <para>The default value is <literal>5000</literal> milliseconds
+ <para>The default value is <literal>5000</literal> milliseconds.
</para>
</section>
@@ -854,7 +980,7 @@
The details of the JGroups configuration won't be discussed here since it is standard JGroups configuration.
Detailed information on JGroups can be found in JGroups release documentation or on-line at
<ulink url="http://www.jgroups.org">http://www.jgroups.org</ulink> or
- <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups">http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups</ulink>
+ <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups">http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups</ulink>.
</para>
</section>
@@ -863,12 +989,12 @@
<para>
JBoss Messaging uses JGroups for all group management. This contains the JGroups stack configuration for the data channel.
</para>
- <para>The data channel is used for sending sending/receiving messages from other nodes in the cluster</para>
+ <para>The data channel is used for sending sending/receiving messages from other nodes in the cluster.</para>
<para>
The details of the JGroups configuration won't be discussed here since it is standard JGroups configuration.
Detailed information on JGroups can be found in JGroups release documentation or on-line at
<ulink url="http://www.jgroups.org">http://www.jgroups.org</ulink> or
- <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups">http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups</ulink>
+ <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups">http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroups</ulink>.
</para>
</section>
@@ -944,7 +1070,9 @@
<depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
- <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
+ <depends optional-attribute-name="TransactionManager">
+ jboss:service=TransactionManager
+ </depends>
<!-- The datasource to use for the persistence manager -->
@@ -959,43 +1087,74 @@
<attribute name="UsingBatchUpdates">true</attribute>
<attribute name="SqlProperties"><![CDATA[
- CREATE_MESSAGE=CREATE TABLE JBM_MSG (MESSAGE_ID BIGINT, RELIABLE CHAR(1), EXPIRATION BIGINT, TIMESTAMP BIGINT, PRIORITY TINYINT, HEADERS MEDIUMBLOB, PAYLOAD LONGBLOB, CHANNEL_COUNT INTEGER, TYPE TINYINT, PRIMARY KEY (MESSAGE_ID)) ENGINE = INNODB
- CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF (CHANNEL_ID BIGINT, MESSAGE_ID BIGINT REFERENCES JBM_MSG(MESSAGE_ID), TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY(CHANNEL_ID, MESSAGE_ID)) ENGINE = INNODB
+ CREATE_MESSAGE=CREATE TABLE JBM_MSG (MESSAGE_ID BIGINT, RELIABLE CHAR(1),
+ EXPIRATION BIGINT, TIMESTAMP BIGINT, PRIORITY TINYINT, HEADERS MEDIUMBLOB,
+ PAYLOAD LONGBLOB, CHANNEL_COUNT INTEGER, TYPE TINYINT, PRIMARY KEY (MESSAGE_ID))
+ ENGINE = INNODB
+ CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF (CHANNEL_ID BIGINT,
+ MESSAGE_ID BIGINT REFERENCES JBM_MSG(MESSAGE_ID), TRANSACTION_ID BIGINT,
+ STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER,
+ SCHED_DELIVERY BIGINT, PRIMARY KEY(CHANNEL_ID, MESSAGE_ID)) ENGINE = INNODB
CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JBM_MSG_REF_TX ON JBM_MSG_REF (TRANSACTION_ID)
CREATE_IDX_MESSAGE_REF_ORD=CREATE INDEX JBM_MSG_REF_ORD ON JBM_MSG_REF (ORD)
CREATE_IDX_MESSAGE_REF_PAGE_ORD=CREATE INDEX JBM_MSG_REF_PAGE_ORD ON JBM_MSG_REF (PAGE_ORD)
- CREATE_IDX_MESSAGE_REF_MESSAGE_ID=CREATE INDEX JBM_MSG_REF_MESSAGE_ID ON JBM_MSG_REF (MESSAGE_ID)
- CREATE_IDX_MESSAGE_REF_SCHED_DELIVERY=CREATE INDEX JBM_MSG_REF_SCHED_DELIVERY ON JBM_MSG_REF (SCHED_DELIVERY)
- CREATE_TRANSACTION=CREATE TABLE JBM_TX (NODE_ID INTEGER, TRANSACTION_ID BIGINT, BRANCH_QUAL VARBINARY(254), FORMAT_ID INTEGER, GLOBAL_TXID VARBINARY(254), PRIMARY KEY (TRANSACTION_ID)) ENGINE = INNODB
- CREATE_COUNTER=CREATE TABLE JBM_COUNTER (NAME VARCHAR(255), NEXT_ID BIGINT, PRIMARY KEY(NAME)) ENGINE = INNODB
- INSERT_MESSAGE_REF=INSERT INTO JBM_MSG_REF (CHANNEL_ID, MESSAGE_ID, TRANSACTION_ID, STATE, ORD, PAGE_ORD, DELIVERY_COUNT, SCHED_DELIVERY) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
+ CREATE_IDX_MESSAGE_REF_MESSAGE_ID=CREATE INDEX JBM_MSG_REF_MESSAGE_ID
+ ON JBM_MSG_REF (MESSAGE_ID)
+ CREATE_IDX_MESSAGE_REF_SCHED_DELIVERY=CREATE INDEX JBM_MSG_REF_SCHED_DELIVERY
+ ON JBM_MSG_REF (SCHED_DELIVERY)
+ CREATE_TRANSACTION=CREATE TABLE JBM_TX (NODE_ID INTEGER, TRANSACTION_ID BIGINT,
+ BRANCH_QUAL VARBINARY(254), FORMAT_ID INTEGER, GLOBAL_TXID VARBINARY(254),
+ PRIMARY KEY (TRANSACTION_ID)) ENGINE = INNODB
+ CREATE_COUNTER=CREATE TABLE JBM_COUNTER (NAME VARCHAR(255), NEXT_ID BIGINT,
+ PRIMARY KEY(NAME)) ENGINE = INNODB
+ INSERT_MESSAGE_REF=INSERT INTO JBM_MSG_REF (CHANNEL_ID, MESSAGE_ID, TRANSACTION_ID,
+ STATE, ORD, PAGE_ORD, DELIVERY_COUNT, SCHED_DELIVERY)
+ VALUES (?, ?, ?, ?, ?, ?, ?, ?)
DELETE_MESSAGE_REF=DELETE FROM JBM_MSG_REF WHERE MESSAGE_ID=? AND CHANNEL_ID=? AND STATE='C'
- UPDATE_MESSAGE_REF=UPDATE JBM_MSG_REF SET TRANSACTION_ID=?, STATE='-' WHERE MESSAGE_ID=? AND CHANNEL_ID=? AND STATE='C'
+ UPDATE_MESSAGE_REF=UPDATE JBM_MSG_REF SET TRANSACTION_ID=?, STATE='-'
+ WHERE MESSAGE_ID=? AND CHANNEL_ID=? AND STATE='C'
UPDATE_PAGE_ORDER=UPDATE JBM_MSG_REF SET PAGE_ORD = ? WHERE MESSAGE_ID=? AND CHANNEL_ID=?
- COMMIT_MESSAGE_REF1=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = NULL WHERE TRANSACTION_ID=? AND STATE='+'
+ COMMIT_MESSAGE_REF1=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = NULL
+ WHERE TRANSACTION_ID=? AND STATE='+'
COMMIT_MESSAGE_REF2=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? AND STATE='-'
ROLLBACK_MESSAGE_REF1=DELETE FROM JBM_MSG_REF WHERE TRANSACTION_ID=? AND STATE='+'
- ROLLBACK_MESSAGE_REF2=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = NULL WHERE TRANSACTION_ID=? AND STATE='-'
- LOAD_PAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, PAGE_ORD, SCHED_DELIVERY FROM JBM_MSG_REF WHERE CHANNEL_ID = ? AND PAGE_ORD BETWEEN ? AND ? ORDER BY PAGE_ORD
- LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? AND PAGE_ORD IS NULL ORDER BY ORD
- LOAD_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? ORDER BY ORD
- UPDATE_REFS_NOT_PAGED=UPDATE JBM_MSG_REF SET PAGE_ORD = NULL WHERE PAGE_ORD BETWEEN ? AND ? AND CHANNEL_ID=?
- SELECT_MIN_MAX_PAGE_ORD=SELECT MIN(PAGE_ORD), MAX(PAGE_ORD) FROM JBM_MSG_REF WHERE CHANNEL_ID = ?
+ ROLLBACK_MESSAGE_REF2=UPDATE JBM_MSG_REF SET STATE='C', TRANSACTION_ID = NULL
+ WHERE TRANSACTION_ID=? AND STATE='-'
+ LOAD_PAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, PAGE_ORD, SCHED_DELIVERY
+ FROM JBM_MSG_REF WHERE CHANNEL_ID = ? AND PAGE_ORD BETWEEN ? AND ?
+ ORDER BY PAGE_ORD
+ LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY
+ FROM JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? AND PAGE_ORD IS NULL
+ ORDER BY ORD
+ LOAD_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM JBM_MSG_REF
+ WHERE STATE = 'C' AND CHANNEL_ID = ? ORDER BY ORD
+ UPDATE_REFS_NOT_PAGED=UPDATE JBM_MSG_REF SET PAGE_ORD = NULL WHERE PAGE_ORD
+ BETWEEN ? AND ? AND CHANNEL_ID=?
+ SELECT_MIN_MAX_PAGE_ORD=SELECT MIN(PAGE_ORD), MAX(PAGE_ORD) FROM JBM_MSG_REF
+ WHERE CHANNEL_ID = ?
SELECT_EXISTS_REF_MESSAGE_ID=SELECT MESSAGE_ID FROM JBM_MSG_REF WHERE MESSAGE_ID = ?
- UPDATE_DELIVERY_COUNT=UPDATE JBM_MSG_REF SET DELIVERY_COUNT = ? WHERE CHANNEL_ID = ? AND MESSAGE_ID = ?
+ UPDATE_DELIVERY_COUNT=UPDATE JBM_MSG_REF SET DELIVERY_COUNT = ? WHERE CHANNEL_ID = ?
+ AND MESSAGE_ID = ?
UPDATE_CHANNEL_ID=UPDATE JBM_MSG_REF SET CHANNEL_ID = ? WHERE CHANNEL_ID = ?
- LOAD_MESSAGES=SELECT MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, HEADERS, PAYLOAD, TYPE FROM JBM_MSG
- INSERT_MESSAGE=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, HEADERS, PAYLOAD, CHANNEL_COUNT, TYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)
+ LOAD_MESSAGES=SELECT MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, HEADERS,
+ PAYLOAD, TYPE FROM JBM_MSG
+ INSERT_MESSAGE=INSERT INTO JBM_MSG (MESSAGE_ID, RELIABLE, EXPIRATION, TIMESTAMP,
+ PRIORITY, HEADERS, PAYLOAD, CHANNEL_COUNT, TYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)
INC_CHANNEL_COUNT=UPDATE JBM_MSG SET CHANNEL_COUNT = CHANNEL_COUNT + 1 WHERE MESSAGE_ID=?
DEC_CHANNEL_COUNT=UPDATE JBM_MSG SET CHANNEL_COUNT = CHANNEL_COUNT - 1 WHERE MESSAGE_ID=?
DELETE_MESSAGE=DELETE FROM JBM_MSG WHERE MESSAGE_ID=? AND CHANNEL_COUNT=0
MESSAGE_ID_COLUMN=MESSAGE_ID
MESSAGE_EXISTS=SELECT MESSAGE_ID FROM JBM_MSG WHERE MESSAGE_ID = ? FOR UPDATE
- INSERT_TRANSACTION=INSERT INTO JBM_TX (NODE_ID, TRANSACTION_ID, BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID) VALUES(?, ?, ?, ?, ?)
+ INSERT_TRANSACTION=INSERT INTO JBM_TX (NODE_ID, TRANSACTION_ID, BRANCH_QUAL, FORMAT_ID,
+ GLOBAL_TXID)
+ VALUES(?, ?, ?, ?, ?)
DELETE_TRANSACTION=DELETE FROM JBM_TX WHERE NODE_ID = ? AND TRANSACTION_ID = ?
- SELECT_PREPARED_TRANSACTIONS=SELECT TRANSACTION_ID, BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID FROM JBM_TX WHERE NODE_ID = ?
- SELECT_MESSAGE_ID_FOR_REF=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF WHERE TRANSACTION_ID = ? AND STATE = '+' ORDER BY ORD
- SELECT_MESSAGE_ID_FOR_ACK=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF WHERE TRANSACTION_ID = ? AND STATE = '-' ORDER BY ORD
+ SELECT_PREPARED_TRANSACTIONS=SELECT TRANSACTION_ID, BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID
+ FROM JBM_TX WHERE NODE_ID = ?
+ SELECT_MESSAGE_ID_FOR_REF=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF
+ WHERE TRANSACTION_ID = ? AND STATE = '+' ORDER BY ORD
+ SELECT_MESSAGE_ID_FOR_ACK=SELECT MESSAGE_ID, CHANNEL_ID FROM JBM_MSG_REF
+ WHERE TRANSACTION_ID = ? AND STATE = '-' ORDER BY ORD
UPDATE_COUNTER=UPDATE JBM_COUNTER SET NEXT_ID = ? WHERE NAME=?
SELECT_COUNTER=SELECT NEXT_ID FROM JBM_COUNTER WHERE NAME=? FOR UPDATE
INSERT_COUNTER=INSERT INTO JBM_COUNTER (NAME, NEXT_ID) VALUES (?, ?)
@@ -1108,19 +1267,26 @@
<para>Here is an example JMSUserManager configuration</para>
- <programlisting>
+ <programlisting wrap-option="true">
<mbean code="org.jboss.jms.server.plugin.JDBCJMSUserManagerService"
name="jboss.messaging:service=JMSUserManager"
xmbean-dd="xmdesc/JMSUserManager-xmbean.xml">
<depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
- <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
+ <depends optional-attribute-name="TransactionManager">
+ jboss:service=TransactionManager
+ </depends>
<attribute name="DataSource">java:/DefaultDS</attribute>
<attribute name="CreateTablesOnStartup">true</attribute>
<attribute name="SqlProperties"><![CDATA[
-CREATE_USER_TABLE=CREATE TABLE JBM_USER (USER_ID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128), PRIMARY KEY(USER_ID)) ENGINE = INNODB
-CREATE_ROLE_TABLE=CREATE TABLE JBM_ROLE (ROLE_ID VARCHAR(32) NOT NULL, USER_ID VARCHAR(32) NOT NULL, PRIMARY KEY(USER_ID, ROLE_ID)) ENGINE = INNODB
+CREATE_USER_TABLE=CREATE TABLE JBM_USER (USER_ID VARCHAR(32) NOT NULL,
+ PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128),
+ PRIMARY KEY(USER_ID)) ENGINE = INNODB
+CREATE_ROLE_TABLE=CREATE TABLE JBM_ROLE (ROLE_ID VARCHAR(32) NOT NULL,
+ USER_ID VARCHAR(32) NOT NULL, PRIMARY KEY(USER_ID, ROLE_ID))
+ ENGINE = INNODB
SELECT_PRECONF_CLIENTID=SELECT CLIENTID FROM JBM_USER WHERE USER_ID=?
-POPULATE.TABLES.1=INSERT INTO JBM_USER (USER_ID,PASSWD,CLIENTID) VALUES ('dilbert','dogbert','dilbert-id')
+POPULATE.TABLES.1=INSERT INTO JBM_USER (USER_ID,PASSWD,CLIENTID)
+ VALUES ('dilbert','dogbert','dilbert-id')
]]></attribute>
</mbean>
</programlisting>
@@ -1204,7 +1370,9 @@
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=DLQ"
xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
@@ -1212,7 +1380,9 @@
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=testTopic"
xmbean-dd="xmdesc/Topic-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="SecurityConfig">
<security>
@@ -1226,7 +1396,9 @@
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=securedTopic"
xmbean-dd="xmdesc/Topic-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="SecurityConfig">
<security>
@@ -1239,7 +1411,9 @@
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=testQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="SecurityConfig">
<security>
@@ -1253,7 +1427,9 @@
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=A"
xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
@@ -1264,40 +1440,58 @@
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=PrivateDLQ"
xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
- <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
- <attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
+ <attribute name="DLQ">
+ jboss.messaging.destination:service=Queue,name=PrivateDLQ
+ </attribute>
+ <attribute name="ExpiryQueue">
+ jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue
+ </attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=TopicWithOwnDLQAndExpiryQueue"
xmbean-dd="xmdesc/Topic-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
- <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
- <attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
+ <attribute name="DLQ">
+ jboss.messaging.destination:service=Queue,name=PrivateDLQ
+ </attribute>
+ <attribute name="ExpiryQueue">
+ jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue
+ </attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=TopicWithOwnRedeliveryDelay"
xmbean-dd="xmdesc/Topic-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="RedeliveryDelay">5000</attribute>
</mbean>
@@ -1306,7 +1500,9 @@
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=testDistributedTopic"
xmbean-dd="xmdesc/Topic-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="Clustered">true</attribute>
</mbean>
@@ -1499,7 +1695,8 @@
Message msg = sess.createMessage();
- msg.setLongProperty(JBossMessage.JMS_JBOSS_SCHEDULED_DELIVERY_PROP_NAME, now + 1000 * 60 * 60 * 2);
+ msg.setLongProperty(JBossMessage.JMS_JBOSS_SCHEDULED_DELIVERY_PROP_NAME,
+ now + 1000 * 60 * 60 * 2);
prod.send(msg);
@@ -2035,8 +2232,12 @@
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=MyConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
- <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
+ <depends optional-attribute-name="ServerPeer">
+ jboss.messaging:service=ServerPeer
+ </depends>
+ <depends optional-attribute-name="Connector">
+ jboss.messaging:service=Connector,transport=bisocket
+ </depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="JNDIBindings">
Modified: trunk/docs/userguide/en/modules/installation.xml
===================================================================
--- trunk/docs/userguide/en/modules/installation.xml 2007-09-26 19:23:42 UTC (rev 3142)
+++ trunk/docs/userguide/en/modules/installation.xml 2007-09-27 15:41:13 UTC (rev 3143)
@@ -181,22 +181,32 @@
<attribute name="Configuration"><![CDATA[
<config>
<invoker transport="bisocket">
- <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
+ <attribute name="marshaller" isParam="true">
+ org.jboss.jms.wireformat.JMSWireFormat
+ </attribute>
+ <attribute name="unmarshaller" isParam="true">
+ org.jboss.jms.wireformat.JMSWireFormat
+ </attribute>
<attribute name="dataType" isParam="true">jms</attribute>
<attribute name="socket.check_connection" isParam="true">false</attribute>
<attribute name="timeout" isParam="true">0</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">4657</attribute>
<attribute name="leasePeriod">10000</attribute>
- <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
- <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
+ <attribute name="clientSocketClass" isParam="true">
+ org.jboss.jms.client.remoting.ClientSocketWrapper
+ </attribute>
+ <attribute name="serverSocketClass">
+ org.jboss.jms.server.remoting.ServerSocketWrapper
+ </attribute>
<attribute name="numberOfRetries" isParam="true">1</attribute>
<attribute name="numberOfCallRetries" isParam="true">1</attribute>
<attribute name="clientMaxPoolSize" isParam="true">50</attribute>
</invoker>
<handlers>
- <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
+ <handler subsystem="JMS">
+ org.jboss.jms.server.remoting.JMSServerInvocationHandler
+ </handler>
</handlers>
</config>
]]></attribute>
@@ -398,22 +408,32 @@
<attribute name="Configuration"><![CDATA[
<config>
<invoker transport="bisocket">
- <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
+ <attribute name="marshaller" isParam="true">
+ org.jboss.jms.wireformat.JMSWireFormat
+ </attribute>
+ <attribute name="unmarshaller" isParam="true">
+ org.jboss.jms.wireformat.JMSWireFormat
+ </attribute>
<attribute name="dataType" isParam="true">jms</attribute>
<attribute name="socket.check_connection" isParam="true">false</attribute>
<attribute name="timeout" isParam="true">0</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">4657</attribute>
<attribute name="leasePeriod">10000</attribute>
- <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
- <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
+ <attribute name="clientSocketClass" isParam="true">
+ org.jboss.jms.client.remoting.ClientSocketWrapper
+ </attribute>
+ <attribute name="serverSocketClass">
+ org.jboss.jms.server.remoting.ServerSocketWrapper
+ </attribute>
<attribute name="numberOfRetries" isParam="true">1</attribute>
<attribute name="numberOfCallRetries" isParam="true">1</attribute>
<attribute name="clientMaxPoolSize" isParam="true">50</attribute>
</invoker>
<handlers>
- <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
+ <handler subsystem="JMS">
+ org.jboss.jms.server.remoting.JMSServerInvocationHandler
+ </handler>
</handlers>
</config>
]]></attribute>
@@ -572,41 +592,75 @@
....
13:19:14,914 WARN [JDBCPersistenceManager]
-JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently NONE.
- Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
- Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
+JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED,
+but it is currently NONE.
+ Using an isolation level less strict than READ_COMMITTED may lead to
+data consistency problems.
+ Using an isolation level more strict than READ_COMMITTED may lead to
+deadlock.
13:19:15,166 INFO [ServerPeer] JBoss Messaging 1.4.0.CR3 server [0] started
-13:19:15,411 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
-13:19:15,412 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] started
-13:19:15,412 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
-13:19:15,413 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
-13:19:15,449 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
-13:19:15,449 INFO [ConnectionFactory] [/ClusteredConnectionFactory, /ClusteredXAConnectionFactory, java:/ClusteredConnectionFactory, java:/ClusteredXAConnectionFactory] started
-13:19:15,468 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,474 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,476 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,478 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,479 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,482 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,483 INFO [QueueService] Queue[/queue/A] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,485 INFO [QueueService] Queue[/queue/B] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,487 INFO [QueueService] Queue[/queue/C] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,489 INFO [QueueService] Queue[/queue/D] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,490 INFO [QueueService] Queue[/queue/ex] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,501 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,503 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,507 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,508 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,511 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,512 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,514 INFO [QueueService] Queue[/queue/testDistributedQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,519 INFO [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
-13:19:15,809 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
-13:19:15,834 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
+13:19:15,411 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled
+, lease period 10000 milliseconds
+13:19:15,412 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/Connec
+tionFactory, java:/XAConnectionFactory] started
+13:19:15,412 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connect
+ion factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but
+post office is non clustered. So connection factory will *not* support failover
+13:19:15,413 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on co
+nnection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
+but post office is non clustered. So connection factory will *not* support load balanc
+ing
+13:19:15,449 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled
+, lease period 10000 milliseconds
+13:19:15,449 INFO [ConnectionFactory] [/ClusteredConnectionFactory, /ClusteredXAConnectionFac
+tory, java:/ClusteredConnectionFactory, java:/ClusteredXAConnectionFactory] started
+13:19:15,468 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, d
+ownCacheSize=2000
+13:19:15,474 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize
+=2000, downCacheSize=2000
+13:19:15,476 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=200000, pageSize=2
+000, downCacheSize=2000
+13:19:15,478 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=200000, pageSiz
+e=2000, downCacheSize=2000
+13:19:15,479 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=200000, pag
+eSize=2000, downCacheSize=2000
+13:19:15,482 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=200000, pageSize=2
+000, downCacheSize=2000
+13:19:15,483 INFO [QueueService] Queue[/queue/A] started, fullSize=200000, pageSize=2000, dow
+nCacheSize=2000
+13:19:15,485 INFO [QueueService] Queue[/queue/B] started, fullSize=200000, pageSize=2000, dow
+nCacheSize=2000
+13:19:15,487 INFO [QueueService] Queue[/queue/C] started, fullSize=200000, pageSize=2000, dow
+nCacheSize=2000
+13:19:15,489 INFO [QueueService] Queue[/queue/D] started, fullSize=200000, pageSize=2000, dow
+nCacheSize=2000
+13:19:15,490 INFO [QueueService] Queue[/queue/ex] started, fullSize=200000, pageSize=2000, do
+wnCacheSize=2000
+13:19:15,501 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=200000, pageSize=
+2000, downCacheSize=2000
+13:19:15,503 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started, fullSize=200000, p
+ageSize=2000, downCacheSize=2000
+13:19:15,507 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started, fullSiz
+e=200000, pageSize=2000, downCacheSize=2000
+13:19:15,508 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started, fullSiz
+e=200000, pageSize=2000, downCacheSize=2000
+13:19:15,511 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started, fullSize=
+200000, pageSize=2000, downCacheSize=2000
+13:19:15,512 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started, fullSize=
+200000, pageSize=2000, downCacheSize=2000
+13:19:15,514 INFO [QueueService] Queue[/queue/testDistributedQueue] started, fullSize=200000,
+pageSize=2000, downCacheSize=2000
+13:19:15,519 INFO [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=200000,
+pageSize=2000, downCacheSize=2000
+13:19:15,809 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:servic
+e=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
+13:19:15,834 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-consol
+e.war/
13:19:16,322 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
13:19:16,342 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
-13:19:16,480 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 19s:359ms
+13:19:16,480 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA dat
+e=200705111440)] Started in 19s:359ms
</programlisting>
@@ -680,12 +734,16 @@
sanity-check:
init:
- [mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/queue/output/classes
- [mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/classes
+ [mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/queue/output/classe
+s
+ [mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/class
+es
compile:
- [javac] Compiling 5 source files to /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/classes
- [javac] Compiling 1 source file to /home/tim/dev/jboss-messaging/trunk/docs/examples/queue/output/classes
+ [javac] Compiling 5 source files to /home/tim/dev/jboss-messaging/trunk/docs/examples/comm
+on/output/classes
+ [javac] Compiling 1 source file to /home/tim/dev/jboss-messaging/trunk/docs/examples/queue
+/output/classes
run:
[java] Queue /queue/testQueue exists
Modified: trunk/docs/userguide/en/modules/recovery_config.xml
===================================================================
--- trunk/docs/userguide/en/modules/recovery_config.xml 2007-09-26 19:23:42 UTC (rev 3142)
+++ trunk/docs/userguide/en/modules/recovery_config.xml 2007-09-27 15:41:13 UTC (rev 3143)
@@ -21,17 +21,22 @@
Default is NO.
-->
<property name="com.arjuna.ats.jta.supportSubtransactions" value="NO"/>
- <property name="com.arjuna.ats.jta.jtaTMImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/>
+ <property name="com.arjuna.ats.jta.jtaTMImplementation"
+ value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/>
<!--
com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple
-->
- <property name="com.arjuna.ats.jta.jtaUTImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/>
+ <property name="com.arjuna.ats.jta.jtaUTImplementation"
+ value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/>
<!--
com.arjuna.ats.internal.jta.transaction.jts.UserTransactionImple
-->
- <!-- *** Add this line to enable recovery for JMS resources using DefaultJMSProvider *** -->
- <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;DefaultJMSProvider"/>
+ <!--
+ *** Add this line to enable recovery for JMS resources using DefaultJMSProvider ***
+ -->
+ <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
+ value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;DefaultJMSProvider"/>
</properties>
More information about the jboss-cvs-commits
mailing list