Well i do have it working without any issues. In my case the remote queue is 
named queueOn2177 and is deployed on the remote server  using the following 
entry in jbossmq-destinations-service.xml file:

<mbean code="org.jboss.mq.server.jmx.Queue"
  |      name="jboss.mq.destination:service=Queue,name=queueOn2177">
  |     <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
  |   </mbean>

Then on my local machine, i have configured my MDB to look up this remote 
queue, by configuring the same in 3 files, namely ejb-jar.xml, jboss.xml and 
jms-ds.xml as follows:

jboss.xml:

 <message-driven> 
  |             <ejb-name>SomeMDB</ejb-name> 
  |             
<destination-jndi-name>queue/queueOn2177</destination-jndi-name> 
  |             <invoker-bindings>
  |             <invoker>      
  |                
<invoker-proxy-binding-name>MyMDBInvoker</invoker-proxy-binding-name>
  |             </invoker>
  |          </invoker-bindings>
  | 
  |             
  |       </message-driven> 
  | 

<invoker-proxy-bindings>
  |       <invoker-proxy-binding>
  |          <name>MyMDBInvoker</name>
  |          <invoker-mbean>SomeMDB</invoker-mbean>
  |          
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
  |          <proxy-factory-config>
  |             <JMSProviderAdapterJNDI>MyJMSProvider</JMSProviderAdapterJNDI>
  |             
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
  |             <MinimumSize>1</MinimumSize>
  |             <KeepAliveMillis>30000</KeepAliveMillis>
  |             <MaximumSize>15</MaximumSize>
  |             <MaxMessages>1</MaxMessages>
  |             <MDBConfig>
  |                <ReconnectIntervalSec>10</ReconnectIntervalSec>
  |                <DLQConfig>
  |                   <DestinationQueue>queue/DLQ</DestinationQueue>
  |                   <MaxTimesRedelivered>10</MaxTimesRedelivered>
  |                   <TimeToLive>0</TimeToLive>
  |                </DLQConfig>
  |             </MDBConfig>
  |          </proxy-factory-config>
  |       </invoker-proxy-binding>
  |    </invoker-proxy-bindings>

jms-ds.xml:

<mbean code="org.jboss.jms.jndi.JMSProviderLoader" 
  |          
name="jboss.mq:service=JMSProviderLoader,name=RemoteMQProvider,server=ps2177">
  |     <!--this name will be used in jboss.xml-->
  |     <attribute name="ProviderName">MyJMSProvider</attribute>
  |     <!--Points to remote server-->
  |     <attribute name="ProviderUrl">jnp://ps2177:1099</attribute>
  |     <attribute 
name="ProviderAdapterClass">org.jboss.jms.jndi.JBossMQProvider</attribute>
  |     <attribute name="QueueFactoryRef">UIL2XAConnectionFactory</attribute>
  |     <attribute name="TopicFactoryRef">UIL2XAConnectionFactory</attribute>
  |   </mbean>
  |  

ejb-jar.xml:

<message-driven> 
  |         <ejb-name>SomeMDB</ejb-name> 
  |         <ejb-class>mypackage.myClass</ejb-class>
  |         <transaction-type>Container</transaction-type>
  |         <message-driven-destination>
  |           <destination-type>javax.jms.Queue</destination-type>
  |         </message-driven-destination>
  |         
  |   </message-driven>



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

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


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to