[jboss-cvs] JBossAS SVN: r66694 - in branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs: mdbsessionpoolclear and 2 other directories.

[jboss-cvs-commits at lists.jboss.org]

Author: bdecoste
Date: 2007-11-02 16:02:13 -0400 (Fri, 02 Nov 2007)
New Revision: 66694

Added:
   branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/
   branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/deploy/
   branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/deploy/jms/
   branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/deploy/jms/hajndi-jms-ds.xml
   branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/lib/
Log:
[JBPAPP-387] Tests and fixes for EJB2.1 and EJB3.0 MDB session pool failover - simulation of TIBCO EMS session behavior

Added: branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/deploy/jms/hajndi-jms-ds.xml
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/deploy/jms/hajndi-jms-ds.xml	                        (rev 0)
+++ branches/JBPAPP_4_2_0_GA_CP01_JBPAPP-364/ejb3/src/resources/test-configs/mdbsessionpoolclear/deploy/jms/hajndi-jms-ds.xml	2007-11-02 20:02:13 UTC (rev 66694)
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<connection-factories>
+ 
+  <!-- ==================================================================== -->
+  <!-- JMS Stuff                                                            -->
+  <!-- ==================================================================== -->
+
+  <!-- The JMS provider loader -->
+  <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
+	 name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
+    <attribute name="ProviderName">DefaultJMSProvider</attribute>
+    <attribute name="ProviderAdapterClass">
+      org.jboss.jms.jndi.JNDIProviderAdapter
+    </attribute>
+    <!-- The combined connection factory -->
+    <attribute name="FactoryRef">XAConnectionFactory</attribute>
+    <!-- The queue connection factory -->
+    <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
+    <!-- The topic factory -->
+    <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
+    <!-- Access JMS via HAJNDI -->
+    <attribute name="Properties">
+       java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+       java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+       java.naming.provider.url=${jboss.bind.address:localhost}:1100
+       jnp.disableDiscovery=false
+       jnp.partitionName=${jboss.partition.name:DefaultPartition}
+       jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
+       jnp.discoveryPort=1102
+       jnp.discoveryTTL=16
+       jnp.discoveryTimeout=5000
+       jnp.maxRetries=1
+    </attribute>
+  </mbean>
+
+  <!-- The server session pool for Message Driven Beans -->
+  <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
+	 name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
+    <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
+    <attribute name="PoolName">StdJMSPool</attribute>
+    <attribute name="PoolFactoryClass">
+      org.jboss.ejb3.test.mdbsessionpoolclear.TestServerSessionPoolFactory
+    </attribute>
+  </mbean>
+
+  <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
+  <tx-connection-factory>
+    <jndi-name>JmsXA</jndi-name>
+    <xa-transaction/>
+    <rar-name>jms-ra.rar</rar-name>
+    <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
+    <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
+    <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
+    <max-pool-size>20</max-pool-size>
+    <security-domain-and-application>JmsXARealm</security-domain-and-application>
+  </tx-connection-factory>
+
+</connection-factories>