1 Reply Latest reply on Jul 7, 2004 1:54 PM by Amit Basu

    remote queue MDB deployment problem

    Amit Basu Newbie

      I have problem with MDB deployment where it is listening to remote queue. I followed the jboss wiki instructions.

      The error in server.log is :
      2004-07-01 18:14:36,423 INFO [org.jboss.ejb.EjbModule] Deploying HASecondary
      2004-07-01 18:14:36,486 ERROR [org.jboss.ejb.EjbModule] Initialization failed
      org.jboss.deployment.DeploymentException: Failed to find InvokerProxyBindingMetaData for: 'whatever-message-driven-bean'. Check the invoker-proxy-binding-name t
      o invoker-proxy-binding/name mappings in jboss.xml
      at org.jboss.ejb.EjbModule.getWebClassLoader(EjbModule.java:722)
      at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:612)
      at org.jboss.ejb.EjbModule.createMessageDrivenContainer(EjbModule.java:484)

      My settings are as follows:

      jms-ds.xml file:

      DefaultJMSProvider
      172.16.106.37:1099

      org.jboss.jms.jndi.JBossMQProvider

      java:/XAConnectionFactory
      java:/XAConnectionFactory


      jboss.xml file:
      <?xml version="1.0"?>

      <invoker-proxy-binding>
      whatever-message-driven-bean
      <invoker-mbean>default</invoker-mbean>
      <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
      <proxy-factory-config>
      java:/DefaultJMSProvider
      java:/StdJMSPool
      15
      1


      10

      queue/DLQ
      10
      0


      </proxy-factory-config>
      </invoker-proxy-binding>
      <enterprise-beans>
      <message-driven>
      <ejb-name>HASecondary</ejb-name>
      <destination-jndi-name>HA-Q1</destination-jndi-name>
      <invoker-bindings>

      <invoker-proxy-binding-name>whatever-message-driven-bean</invoker-proxy-binding-name>

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

        • 1. Re: remote queue MDB deployment problem
          Amit Basu Newbie

          Couple of workarounds that work
          (for anyone who encounters similar problem with the wiki way):

          - have the MDB listen locally, and the sender send to the remote queue. This works fine.

          - Instead of MDB, just have a JMS message listener that looks up the remote queue and listens to it by creating the receiver on a session on the remote queue.

          I chose the 2nd one, as my queue NEEDED to be on the sender side.

          - amit.