[jboss-user] [JBoss Messaging] - Re: Need help with configuring message bridge from JBM-1.4.0

Karen.Kramer do-not-reply at jboss.com
Thu Sep 11 15:47:28 EDT 2008


Well I was able to get it to work, so this may help you:

Putting everything in one file --- jms-ds.xml, seemed to solve the deployment probem. This following code works successfully for forwarding a message from a queue on a server with JBM and to JBossMQ with the Bridge being deployed on the server using JBM. You would only need to change the queue names and the IP address of the remote server.

This is my jmx-ds.xml file

<?xml version="1.0" encoding="UTF-8" ?> 
  | <connection-factories>
  | 
  | <!--  The JMS provider loader   --> 
  | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider">
  |   <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> 
  |   <!-- 
  |    Uncomment to use HAJNDI to access JMS
  |     <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=localhost:1100
  |     </attribute>
  |   --> 
  | </mbean>
  | 
  | 
  | 
  | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider">
  |      <attribute name="ProviderName">RemoteXAConnectionFactory</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>
  |     <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=172.31.19.57:1399
  |     </attribute>
  |   </mbean>
  |   
  |   <mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=TestBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
  |      <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
  |      <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends>
  |      <attribute name="SourceDestinationLookup">/queue/DisputeStatusMessageQueue</attribute>
  |      <attribute name="TargetDestinationLookup">/queue/DisputeStatusMessageQueue</attribute>
  |      <attribute name="QualityOfServiceMode">0</attribute>
  |      <attribute name="MaxBatchSize">5</attribute>
  |      <attribute name="MaxBatchTime">-1</attribute>
  |      <attribute name="FailureRetryInterval">5000</attribute>
  |      <attribute name="MaxRetries">-1</attribute>
  |      <attribute name="AddMessageIDInHeader">false</attribute>
  | </mbean>
  | 
  | <!--  The server session pool for Message Driven Beans --> 
  | <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> 
  |   <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>

Good Luck!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175971#4175971

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175971



More information about the jboss-user mailing list