• 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
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

MDB Vs Message Listener performance

 
Ranch Hand
Posts: 1491
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JMS destination(either only one Queue or only one Topic) delivers message to the particular MDB instance deployed in the EJB container. (If we need
to deliver multiple messages simultaneously, then we can instantiate multpile MDB instances )

But if we use simple JMS listener, we can send multiple JMS destination( more than one Queue and Topic) delivers messages to the JMS consumer.
EJB container provides concurrent request to the MDB(Scalability), transaction, security and MDB life cycle management.

Which gives best performance MDB (needs EJB container, but takes care many of the features like Transaction, security, etc) or JMS consumer(no need of
EJB container, we have to take care all the EJB container provided services ?
 
kri shan
Ranch Hand
Posts: 1491
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Any update ?
 
kri shan
Ranch Hand
Posts: 1491
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
reply ?
 
reply
    Bookmark Topic Watch Topic
  • New Topic