MDP consuming from remote JBossMQ Queue

[Steven Landers]

Hi there-

I have a HA-JNDI JBossMQ queue hosted by JBoss 4.0.4 and an MDP that works when the MDP is deployed on the same container as the queue. When I put the MDP on another server, the subscriber count increases from 0 on the queue box, but the MDP is never called, and messages remain in the Queue. I'm using Spring 2.0 to wire the MDP to the queue.

Here is my Spring configuration:

    

<bean id="queueJndiTemplate" class="org.springframework.jndi.JndiTemplate">
        <property name="environment">
            <props>
            <prop key="java.naming.provider.url">jnp://servername:1100</prop>
            <prop key="java.naming.factory.url.pkgs">org.jnp.interfaces:org.jboss.naming</prop>
            <prop key="java.naming.factory.initial">org.jnp.interfaces.NamingContextFactory</prop>
            </props>
        </property>
    </bean>

    <bean id="queueConnectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
        <property name="jndiTemplate">
            <ref bean="queueJndiTemplate"/>
        </property>
        <property name="jndiName">
            <value>ConnectionFactory</value>
        </property>
    </bean>


<bean id="queueDestinationResolver" class="org.springframework.jms.support.destination.JndiDestinationResolver">
        <property name="jndiTemplate" ref="queueJndiTemplate"/>
        <property name="cache" value="false"/>
    </bean>

<bean id="queuePrototypeListenerContainer"
           class="org.springframework.jms.listener.DefaultMessageListenerContainer"
           abstract="true">
        <property name="concurrentConsumers" ref="transcodingThreads" />
        <property name="connectionFactory" ref="queueConnectionFactory" />
        <property name="destinationResolver" ref="queueDestinationResolver" />
        <!-- 2 is CLIENT_ACKNOWLEDGE: http://java.sun.com/j2ee/1.4/docs/api/constant-values.html#javax.jms.Session.CLIENT_ACKNOWLEDGE -->
        <!-- 1 is auto acknowledge -->
        <property name="sessionAcknowledgeMode" value="1" />
        <property name="sessionTransacted" value="true" />
    </bean>

<bean id="queueMDPListener"
              class="com.comp.myMDBConsumer">
                  <property name="prop1" ref="val1" />
                  <property name="prop2" ref="val2" />
                  <property name="prop3" ref="val3" />
        </bean>

<bean id="queueDestination" class="org.springframework.jndi.JndiObjectFactoryBean">
        <property name="jndiTemplate" ref="queueJndiTemplate" />
        <property name="jndiName" value="queue/globalQueue" />
    </bean>

<bean id="queueMDPContainer" parent="queuePrototypeListenerContainer">
           <property name="destination" ref="queueDestination" />
           <property name="messageListener" ref="queueMDPListener" />
 </bean>

- When I deploy the MDP on servername, it works fine. All messages are processed.
- When I deploy the MDP elsewhere, however, the MDP isn't called. The Queue is subscribed to (seen as 25 in jmx-console), and upon undeploying the queue itself, I get JMS Exceptions on the MDP server...indicating that there is some awareness of the queue.

Does anyone know why that is? Why does the MDP have to be on the same server as the queue for this?

Thanks,
Steven

[Steven Landers]

I found the issue: It was actually receiving the message, but logging was misconfigured so I couldn't find an application-specific error I was having - nor could I see the message arrive. All is fixed - The servername server had the correct configuration - thus the difference in behavior.