3 Replies Latest reply on Sep 8, 2004 7:11 AM by jrobette

    Can't get MDB listening to a remote Queue !

    jrobette
    jrobette Sep 7, 2004 11:33 AM

      Hi everyone,

      I'm a bit puzzled with connecting a remote queue to an ejb.
      In fact, i've 2 Jboss servers on 2 computers. The first one defines a queue called Q_INCOMING. The second one defines an MDB which should listen to that queue.

      I've been searching everywhere without getting it running. I don't have any error but when i populate the Q_INCOMING, the MDB doesn't react at all!

      I'm sure it is something easy that most of you have already done. So please, i desperately need help...

      Thanks in advance.

      PS : sorry for my english which my not be very accurate

      Here are my files.

      Definition of Q_INCOMING on server 1 :

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


      On server 2 :

      I've this myjms-ds.xml file in the deploy directory : 

      <connection-factories >

 <mbean code= "org.jboss.jms.jndi.JMSProviderLoader" name= "jboss.mq:service=JMSProviderLoader,name=RemoteMQProvider,server=ClientServer" >
 <attribute name= "ProviderName">ClientJMSProvider</attribute >
 <attribute name= "ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute >
 <attribute name= "QueueFactoryRef">java:/XAConnectionFactory</attribute >
 <attribute name= "TopicFactoryRef">java:/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=jnp://10.40.1.47:1099
 </attribute>

 </mbean >
</connection-factories >


      I've this jboss.xml in my MDB : 
      <jboss>
 <enterprise-beans>
 <message-driven>
 <ejb-name>authenticator</ejb-name>
 <destination-jndi-name>queue/Q_INCOMING</destination-jndi-name>
 <invoker-bindings>
 <invoker>
 <invoker-proxy-binding-name>my-message-driven-bean</invoker-proxy-binding-name>
 </invoker>
 </invoker-bindings>

 </message-driven>
 </enterprise-beans>



 <invoker-proxy-bindings>
 <invoker-proxy-binding>
 <name>my-message-driven-bean</name>
 <invoker-mbean>my-message-driven-bean</invoker-mbean>
 <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
 <proxy-factory-config>
 <JMSProviderAdapterJNDI>ClientJMSProvider</JMSProviderAdapterJNDI>
 <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
 <MaximumSize>10</MaximumSize>
 <MaxMessages>10</MaxMessages>
 <MDBConfig>
 <ReconnectIntervalSec>1</ReconnectIntervalSec>
 <DLQConfig>
 <DestinationQueue>queue/DLQ</DestinationQueue>
 <MaxTimesRedelivered>3</MaxTimesRedelivered>
 <TimeToLive>0</TimeToLive>
 </DLQConfig>
 </MDBConfig>
 </proxy-factory-config>
 </invoker-proxy-binding>
 </invoker-proxy-bindings>

</jboss >



      • 2919 Views
      • Tags: