• 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:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

MQSeries / JMS Durable Subscriber

 
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
In MQSeries the message will be stored in SYSTEM.JMS.D.SUBSCRIBER.QUEUE. Then the DurableSubscriber can retrieve all the messages.
What about JMS for Durable Subscription i.e. where it will store the messages.
Regards,
M.S.Raman.
 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
i'm not sure i understand your question but if you mean where is the information about the durable subscriber it self then the MQ has an admin queue(i think it's SYSTEM.JMS.ADMIN.QUEUE) and also he has queue for the broker that also saves details about the subscribers(i think it's something like SYSTEM.BROKER.IO....).
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic