[embjopr-commits] EMBJOPR SVN: r288 - in trunk/jsfunit: testdata/jboss-configuration/deploy and 1 other directory.

Author: fjuma Date: 2009-04-14 17:04:48 -0400 (Tue, 14 Apr 2009) New Revision: 288 Added: trunk/jsfunit/testdata/jboss-configuration/deploy/messaging-service.xml Modified: trunk/jsfunit/pom.xml Log: Setting the "EnableMessageCounters" property to true for the JMS metrics tests. Modified: trunk/jsfunit/pom.xml =================================================================== --- trunk/jsfunit/pom.xml 2009-04-14 19:06:45 UTC (rev 287) +++ trunk/jsfunit/pom.xml 2009-04-14 21:04:48 UTC (rev 288) @@ -325,6 +325,10 @@ <file>${basedir}/testdata/jboss-configuration/conf/props/jmx-console-users.properties</file> <tofile>conf/props/jmx-console-users.properties</tofile> </configfile> + <configfile> + <file>${basedir}/testdata/jboss-configuration/deploy/messaging-service.xml</file> + <tofile>deploy/messaging/messaging-service.xml</tofile> + </configfile> </configfiles> <!-- Deploy the test files --> Added: trunk/jsfunit/testdata/jboss-configuration/deploy/messaging-service.xml =================================================================== --- trunk/jsfunit/testdata/jboss-configuration/deploy/messaging-service.xml (rev 0) +++ trunk/jsfunit/testdata/jboss-configuration/deploy/messaging-service.xml 2009-04-14 21:04:48 UTC (rev 288) @@ -0,0 +1,108 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<!-- + The JBoss Messaging service deployment descriptor. + + $Id: messaging-service.xml 85945 2009-03-16 19:45:12Z dimitris(a)jboss.org $ + --> + +<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">${jboss.messaging.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 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> + + <!-- 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> + + <!-- 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> + + <!-- Set to true to enable message counters that can be viewed via JMX --> + + <attribute name="EnableMessageCounters">true</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> + --> + + <!-- The name of the server aspects configuration resource + <attribute name="ServerAopConfig">aop/jboss-aop-messaging-server.xml</attribute> + --> + <!-- The name of the client aspects configuration resource + <attribute name="ClientAopConfig">aop/jboss-aop-messaging-client.xml</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> + <depends optional-attribute-name="SecurityStore" + proxy-type="org.jboss.jms.server.SecurityStore">jboss.messaging:service=SecurityStore</depends> + </mbean> + +</server>