• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

MDP consuming from remote JBossMQ Queue

 
Steven Landers
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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:



- 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
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic