[jboss-cvs] jboss-seam/bootstrap/deploy/messaging ...
Ales Justin
ajustin at redhat.com
Tue Nov 13 11:12:08 EST 2007
User: alesj
Date: 07/11/13 11:12:08
Modified: bootstrap/deploy/messaging
hsqldb-persistence-service.xml remoting-service.xml
connection-factories-service.xml
destinations-service.xml legacy-service.xml
messaging-service.xml jms-ds.xml
Log:
Changing message mbeans to the ones built at Embedded build in AS5_trunk.
TODO - where there some Seam specific settings?
Revision Changes Path
1.3 +63 -6 jboss-seam/bootstrap/deploy/messaging/hsqldb-persistence-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: hsqldb-persistence-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/hsqldb-persistence-service.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- hsqldb-persistence-service.xml 12 Nov 2007 21:06:10 -0000 1.2
+++ hsqldb-persistence-service.xml 13 Nov 2007 16:12:08 -0000 1.3
@@ -3,44 +3,101 @@
<!--
Hypersonic persistence deployment descriptor.
- $Id: hsqldb-persistence-service.xml,v 1.2 2007/11/12 21:06:10 alesj Exp $
+ DO NOT USE HYPERSONIC IN PRODUCTION or in a clustered environment- Hypersonic does not have transaction isolation
+
+ $Id: hsqldb-persistence-service.xml,v 1.3 2007/11/13 16:12:08 alesj Exp $
-->
<server>
+ <!-- Persistence Manager MBean configuration
+ ======================================= -->
+
<mbean code="org.jboss.messaging.core.jmx.JDBCPersistenceManagerService"
name="jboss.messaging:service=PersistenceManager"
xmbean-dd="xmdesc/JDBCPersistenceManager-xmbean.xml">
+
<depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
+
<depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager</depends>
+
+ <!-- The datasource to use for the persistence manager -->
+
<attribute name="DataSource">java:/DefaultDS</attribute>
+
+ <!-- If true will attempt to create tables and indexes on every start-up -->
+
<attribute name="CreateTablesOnStartup">true</attribute>
+
+ <!-- If true then will use JDBC batch updates -->
+
<attribute name="UsingBatchUpdates">false</attribute>
+
+ <!-- The maximum number of parameters to include in a prepared statement -->
+
<attribute name="MaxParams">500</attribute>
</mbean>
- <!-- Note that Hypersonic CANNOT be used for clustered post offices -->
+ <!-- Messaging Post Office MBean configuration
+ ========================================= -->
<mbean code="org.jboss.messaging.core.jmx.MessagingPostOfficeService"
name="jboss.messaging:service=PostOffice"
xmbean-dd="xmdesc/MessagingPostOffice-xmbean.xml">
+
<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>
- <attribute name="PostOfficeName">JMS</attribute>
+
+ <!-- The name of the post office -->
+
+ <attribute name="PostOfficeName">JMS post office</attribute>
+
+ <!-- The datasource used by the post office to access it's binding information -->
+
<attribute name="DataSource">java:/DefaultDS</attribute>
+
+ <!-- If true will attempt to create tables and indexes on every start-up -->
+
<attribute name="CreateTablesOnStartup">true</attribute>
+
+ <!-- This post office is NON CLUSTERED - do not use clustering with Hypersonic!! -->
+
+ <attribute name="Clustered">false</attribute>
</mbean>
+ <!-- Messaging JMS User Manager MBean config
+ ======================================= -->
+
<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>
+
<attribute name="DataSource">java:/DefaultDS</attribute>
+
<attribute name="CreateTablesOnStartup">true</attribute>
+
<attribute name="SqlProperties"><![CDATA[
-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) VALUES ('guest', 'guest')
+POPULATE.TABLES.2 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('j2ee', 'j2ee')
+POPULATE.TABLES.3 = INSERT INTO JBM_USER (USER_ID, PASSWD, CLIENTID) VALUES ('john', 'needle', 'DurableSubscriberExample')
+POPULATE.TABLES.4 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('nobody', 'nobody')
+POPULATE.TABLES.5 = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('dynsub', 'dynsub')
+POPULATE.TABLES.6 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('guest','guest')
+POPULATE.TABLES.7 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('j2ee','guest')
+POPULATE.TABLES.8 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('john','guest')
+POPULATE.TABLES.9 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('subscriber','john')
+POPULATE.TABLES.10 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('publisher','john')
+POPULATE.TABLES.11 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('publisher','dynsub')
+POPULATE.TABLES.12 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('durpublisher','john')
+POPULATE.TABLES.13 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('durpublisher','dynsub')
+POPULATE.TABLES.14 = INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('noacc','nobody')
]]></attribute>
</mbean>
1.2 +62 -78 jboss-seam/bootstrap/deploy/messaging/remoting-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: remoting-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/remoting-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- remoting-service.xml 15 Jun 2007 05:20:58 -0000 1.1
+++ remoting-service.xml 13 Nov 2007 16:12:08 -0000 1.2
@@ -1,78 +1,62 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
- Messaging Remoting service deployment descriptor.
+ Standard bisocket-based Remoting service deployment descriptor.
- $Id: remoting-service.xml,v 1.1 2007/06/15 05:20:58 gavin Exp $
+ $Id: remoting-service.xml,v 1.2 2007/11/13 16:12:08 alesj Exp $
-->
<server>
+ <!-- Standard bisocket connector - the bisocket transport only opens connection from client->server
+ so can be used with firewalls where only outgoing connections are allowed.
+ For examples of HTTP and SSL transports see docs/examples -->
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.messaging:service=Connector,transport=bisocket"
- display-name="Bisocket transport Connector">
+ display-name="Bisocket Transport Connector">
<attribute name="Configuration">
<config>
<invoker transport="bisocket">
- <attribute name="marshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
- <!-- Serialization type must be jms - do not change! -->
- <attribute name="serializationtype" isParam="true">jms</attribute>
+
+ <!-- There should be no reason to change these parameters - warning!
+ Changing them may stop JBoss Messaging working correctly -->
+ <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">0</attribute>
+ <attribute name="timeout" isParam="true">0</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">4457</attribute>
- <attribute name="leasePeriod">10000</attribute>
- <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</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="callbackErrorsAllowed">1</attribute>
- <attribute name="numberOfRetries" isParam="true">1</attribute>
- <attribute name="NumberOfCallRetries" isParam="true">2</attribute>
- <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
- </invoker>
- <handlers>
- <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
- </handlers>
- </config>
- </attribute>
- <depends>jboss.messaging:service=NetworkRegistry</depends>
- </mbean>
-
- <!--
- HTTP Connector example
+ <attribute name="numberOfCallRetries" isParam="true">1</attribute>
+ <attribute name="pingFrequency" isParam="true">214748364</attribute>
+ <attribute name="pingWindowFactor" isParam="true">10</attribute>
+ <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
+ <!-- End immutable parameters -->
+
+ <!-- Periodicity of client pings. Server window by default is twice this figure -->
+ <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
+
+ <!-- Number of seconds to wait for a connection in the client pool to become free -->
+ <attribute name="numberOfRetries" isParam="true">10</attribute>
+
+ <!-- Max Number of connections in client pool. This should be significantly higher than
+ the max number of sessions/consumers you expect -->
+ <attribute name="clientMaxPoolSize" isParam="true">200</attribute>
+
+ <!-- Use these parameters to specify values for binding and connecting control connections to
+ work with your firewall/NAT configuration
+ <attribute name="secondaryBindPort">xyz</attribute>
+ <attribute name="secondaryConnectPort">abc</attribute>
-->
- <!--
- <mbean code="org.jboss.remoting.transport.Connector"
- name="jboss.messaging:service=Connector,transport=http"
- display-name="HTTP transport Connector">
- <attribute name="Configuration">
- <config>
- <invoker transport="http">
- <attribute name="marshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
- <!== Serialization type must be jms - do not change! ==>
- <attribute name="serializationtype" isParam="true">jms</attribute>
- <attribute name="dataType" isParam="true">jms</attribute>
- <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
- <attribute name="serverBindPort">4458</attribute>
- <attribute name="leasePeriod">20000</attribute>
- <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
- <attribute name="callbackPollPeriod" isParam="true">100</attribute>
+
</invoker>
<handlers>
<handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
</handlers>
</config>
</attribute>
- <depends>jboss.messaging:service=NetworkRegistry</depends>
</mbean>
- -->
-
-
- <!-- TODO: Do I need this> -->
- <mbean code="org.jboss.remoting.network.NetworkRegistry"
- name="jboss.messaging:service=NetworkRegistry"/>
</server>
\ No newline at end of file
1.2 +148 -28 jboss-seam/bootstrap/deploy/messaging/connection-factories-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: connection-factories-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/connection-factories-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- connection-factories-service.xml 15 Jun 2007 05:20:58 -0000 1.1
+++ connection-factories-service.xml 13 Nov 2007 16:12:08 -0000 1.2
@@ -3,11 +3,15 @@
<!--
Messaging Connection Factories deployment descriptor.
- $Id: connection-factories-service.xml,v 1.1 2007/06/15 05:20:58 gavin Exp $
+ $Id: connection-factories-service.xml,v 1.2 2007/11/13 16:12:08 alesj Exp $
-->
<server>
+ <!-- The default connection factory does not support automatic failover or load balancing-
+ this is so we can maintain compatiblity with applications written for JBoss MQ which use this
+ connection factory.
+ -->
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=ConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
@@ -23,7 +27,123 @@
<binding>java:/XAConnectionFactory</binding>
</bindings>
</attribute>
+ </mbean>
+
+ <!-- A clustered connection factory that supports automatic failover and load balancing of created
+ connections.
+ This factory is not suitable to be used by MDBs.
+ -->
+ <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
+ name="jboss.messaging.connectionfactory:service=ClusteredConnectionFactory"
+ 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>jboss.messaging:service=PostOffice</depends>
+
+ <attribute name="JNDIBindings">
+ <bindings>
+ <binding>/ClusteredConnectionFactory</binding>
+ <binding>/ClusteredXAConnectionFactory</binding>
+ <binding>java:/ClusteredConnectionFactory</binding>
+ <binding>java:/ClusteredXAConnectionFactory</binding>
+ </bindings>
+ </attribute>
+ <attribute name="SupportsFailover">true</attribute>
+ <attribute name="SupportsLoadBalancing">true</attribute>
+ </mbean>
+
+ <!-- A connection factory with no JNDI bindings that is used in clustering to create the connections that
+ pull messages from one node to another
+ -->
+ <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
+ name="jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory"
+ 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>jboss.messaging:service=PostOffice</depends>
+ <attribute name="SupportsFailover">false</attribute>
+ <attribute name="SupportsLoadBalancing">false</attribute>
</mbean>
+ <!-- An example connection factory with all attributes shown
+
+ <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
+ name="jboss.messaging.connectionfactory:service=MyExampleConnectionFactory"
+ xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
+
+ <constructor>
+
+ <!- - You can specify the default Client ID to use for connections created using this factory - ->
+
+ <arg type="java.lang.String" value="MyClientID"/>
+
+ </constructor>
+
+ <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+
+ <!- - The transport to use - can be bisocket, sslbisocket or http - ->
+
+ <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=http</depends>
+
+ <depends>jboss.messaging:service=PostOffice</depends>
+
+ <!- - PrefetchSize determines the approximate maximum number of messages the client consumer will buffer locally - ->
+
+ <attribute name="PrefetchSize">150</attribute>
+
+ <!- - Paging params to be used for temporary queues - ->
+
+ <attribute name="DefaultTempQueueFullSize">200000</attribute>
+
+ <attribute name="DefaultTempQueuePageSizeSize">2000</attribute>
+
+ <attribute name="DefaultTempQueueDownCacheSize">2000</attribute>
+
+ <!- - The batch size to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode - ->
+
+ <attribute name="DupsOKBatchSize">5000</attribute>
+
+ <!- - Does this connection factory support automatic failover? - ->
+
+ <attribute name="SupportsFailover">false</attribute>
+
+ <!- - Does this connection factory support automatic client side load balancing? - ->
+
+ <attribute name="SupportsLoadBalancing">false</attribute>
+
+ <!- - The class name of the factory used to create the load balancing policy to use on the client side - ->
+
+ <attribute name="LoadBalancingFactory">org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory</attribute>
+
+ <!- - Whether we should be strict TCK compliant, i.e. how we deal with foreign messages, defaults to false- ->
+
+ <attribute name="StrictTck">false</attribute>
+
+ <!- - Disable JBoss Remoting Connector sanity checks - There is rarely a good reason to set this to true - ->
+
+ <attribute name="DisableRemotingChecks">false</attribute>
+
+ <!- - The connection factory will be bound in the following places in JNDI - ->
+
+ <attribute name="JNDIBindings">
+
+ <bindings>
+
+ <binding>/acme/MyExampleConnectionFactory</binding>
+
+ <binding>/acme/MyExampleConnectionFactoryDupe</binding>
+
+ <binding>java:/xyz/CF1</binding>
+
+ <binding>java:/connectionfactories/acme/connection_factory</binding>
+
+ </bindings>
+
+ </attribute>
+
+ </mbean>
+
+ -->
+
</server>
\ No newline at end of file
1.2 +33 -89 jboss-seam/bootstrap/deploy/messaging/destinations-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: destinations-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/destinations-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- destinations-service.xml 15 Jun 2007 05:20:58 -0000 1.1
+++ destinations-service.xml 13 Nov 2007 16:12:08 -0000 1.2
@@ -3,7 +3,7 @@
<!--
Messaging Destinations deployment descriptor.
- $Id: destinations-service.xml,v 1.1 2007/06/15 05:20:58 gavin Exp $
+ $Id: destinations-service.xml,v 1.2 2007/11/13 16:12:08 alesj Exp $
-->
<server>
@@ -30,61 +30,5 @@
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
- <!--
- Example destinations.
- -->
-
- <!-- It's possible for indiviual queues and topics to use a specific queue for
- an expiry or DLQ -->
-
- <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>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>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>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>
- </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>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>
- </mbean>
-
- <!-- Queues and Topics can also specify their own redelivery delay -->
-
- <mbean code="org.jboss.jms.server.destination.QueueService"
- name="jboss.messaging.destination:service=Queue,name=QueueWithOwnRedeliveryDelay"
- xmbean-dd="xmdesc/Queue-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
- <depends>jboss.messaging:service=PostOffice</depends>
- <attribute name="RedeliveryDelay">5000</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>jboss.messaging:service=PostOffice</depends>
- <attribute name="RedeliveryDelay">5000</attribute>
- </mbean>
</server>
\ No newline at end of file
1.2 +0 -0 jboss-seam/bootstrap/deploy/messaging/legacy-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: legacy-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/legacy-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- legacy-service.xml 15 Jun 2007 05:20:58 -0000 1.1
+++ legacy-service.xml 13 Nov 2007 16:12:08 -0000 1.2
@@ -2,7 +2,7 @@
<!--
Messaging Destinations deployment descriptor.
- $Id: legacy-service.xml,v 1.1 2007/06/15 05:20:58 gavin Exp $
+ $Id: legacy-service.xml,v 1.2 2007/11/13 16:12:08 alesj Exp $
-->
<server>
1.5 +82 -9 jboss-seam/bootstrap/deploy/messaging/messaging-service.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: messaging-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/messaging-service.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- messaging-service.xml 13 Nov 2007 13:48:01 -0000 1.4
+++ messaging-service.xml 13 Nov 2007 16:12:08 -0000 1.5
@@ -3,37 +3,110 @@
<!--
The JBoss Messaging service deployment descriptor.
- $Id: messaging-service.xml,v 1.4 2007/11/13 13:48:01 alesj Exp $
+ $Id: messaging-service.xml,v 1.5 2007/11/13 16:12:08 alesj Exp $
-->
<server>
+ <!-- ServerPeer MBean configuration
+ ============================== -->
+
<mbean code="org.jboss.jms.server.ServerPeer"
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 -->
+
+ <attribute name="ServerPeerID">0</attribute>
+
+ <!-- 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 -->
+
+ <attribute name="DefaultTopicJNDIContext">/topic</attribute>
+
<attribute name="PostOffice">jboss.messaging:service=PostOffice</attribute>
+
+ <!-- The JAAS security domain to use for JBoss Messaging -->
+
<attribute name="SecurityDomain">java:/jaas/messaging</attribute>
+
+ <!-- The default security configuration to apply to destinations - this can be overridden on a per destination basis -->
+
<attribute name="DefaultSecurityConfig">
<security>
+ <role name="Administrator" read="true" write="true" create="true"/>
+ <role name="Manager" read="true" write="true" create="true"/>
<role name="guest" read="true" write="true" create="true"/>
</security>
</attribute>
- <attribute name="ServerPeerID">0</attribute>
- <attribute name="DefaultQueueJNDIContext">/queue</attribute>
- <attribute name="DefaultTopicJNDIContext">/topic</attribute>
+
+ <!-- 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>
+
+ <!-- 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 -->
+
<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 -->
+
<attribute name="DefaultRedeliveryDelay">0</attribute>
- <!--<attribute name="QueueStatsSamplePeriod">5000</attribute>-->
- <attribute name="FailoverStartTimeout">3000</attribute>
- <attribute name="FailoverCompleteTimeout">12000</attribute>
+
+ <!-- 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 -->
+
+ <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 -->
+
+ <attribute name="FailoverCompleteTimeout">300000</attribute>
+
+ <attribute name="StrictTck">false</attribute>
+
+ <!-- The maximum number of days results to maintain in the message counter history -->
+
<attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>
+
+ <!-- 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>
+ <!-- Use XA when pulling persistent messages from a remote node to this one. -->
+
+ <attribute name="UseXAForMessagePull">false</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? -->
+
+ <attribute name="DefaultPreserveOrdering">false</attribute>
+
+ <!-- Max. time to hold previously delivered messages back waiting for clients to reconnect after failover -->
+
+ <attribute name="RecoverDeliveriesTimeout">300000</attribute>
+
+ <!-- The password used by the message sucker connections to create connections.
+ THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM
+ <attribute name="SuckerPassword"></attribute>
+ -->
+
<depends optional-attribute-name="PersistenceManager">jboss.messaging:service=PersistenceManager</depends>
+
<depends optional-attribute-name="JMSUserManager">jboss.messaging:service=JMSUserManager</depends>
+
<depends>jboss.messaging:service=Connector,transport=bisocket</depends>
</mbean>
1.3 +0 -9 jboss-seam/bootstrap/deploy/messaging/jms-ds.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: jms-ds.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/bootstrap/deploy/messaging/jms-ds.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- jms-ds.xml 12 Nov 2007 21:06:10 -0000 1.2
+++ jms-ds.xml 13 Nov 2007 16:12:08 -0000 1.3
@@ -20,15 +20,6 @@
<attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
</mbean>
-<!--
- <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
- name="jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool">
- <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
- <attribute name="PoolName">StdJMSPool</attribute>
- <attribute name="PoolFactoryClass">org.jboss.jms.asf.StdServerSessionPoolFactory</attribute>
- </mbean>
--->
-
<!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
<tx-connection-factory>
<jndi-name>JmsXA</jndi-name>
More information about the jboss-cvs-commits
mailing list