[jboss-user] [JBoss Messaging] - Re: JBoss Messaging RA configuration

[kdeboer]

Thanks for the link. I was aware of this wiki page.
But there is something unclear to me:
If you have a handle to a remote connectionFactory, how can you get a handle to a queue running in a remote server. Is this automatically done in the correct JNDI namespace (the remote server one) or are other tricks needed. That is why i thought about some admin object referencing a remote queue.

The inspiration (or confusement) comes from the way JBoss integrates with ActiveMQ.
Her is a sample of a connection factory and an admin object for the remote queue:




anonymous wrote : <?xml version="1.0" encoding="UTF-8"?>
  | <connection-factories>
  |    <tx-connection-factory>
  |       <jndi-name>activemq/QueueConnectionFactory</jndi-name>
  |       <xa-transaction/>
  |       <track-connection-by-tx/>
  |       <rar-name>activemq-rar-5.1.0.rar</rar-name>
  |       <connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
  |       tcp://messagebroker1:61616
  |       <!--
  |       sa
  |       
  |       -->
  |       <min-pool-size>1</min-pool-size>
  |       <max-pool-size>200</max-pool-size>
  |       <blocking-timeout-millis>30000</blocking-timeout-millis>
  |       <idle-timeout-minutes>3</idle-timeout-minutes>
  |    </tx-connection-factory>
  |    <tx-connection-factory>
  |       <jndi-name>activemq/TopicConnectionFactory</jndi-name>
  |       <xa-transaction/>
  |       <track-connection-by-tx/>
  |       <rar-name>activemq-rar-5.1.0.rar</rar-name>
  |       <connection-definition>javax.jms.TopicConnectionFactory</connection-definition>
  |       tcp://messagebroker1:61616
  |       <!--
  |       sa
  |       
  |       -->
  |       <min-pool-size>1</min-pool-size>
  |       <max-pool-size>200</max-pool-size>
  |       <blocking-timeout-millis>30000</blocking-timeout-millis>
  |       <idle-timeout-minutes>3</idle-timeout-minutes>
  |    </tx-connection-factory>
  |    
  |       queue/receiver
  |       <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-rar-5.1.0.rar'
  | 
  |       javax.jms.Queue
  |       PhysicalName=queue.receiver
  |    
  | </connection-factories>
  | 
  | 
  | 

BTW After doing several tests with ActiveMQ and JBoss Messaging (with clustering and persistency) i chose for Jboss Messaging. 

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

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