File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes MDB Vs  Message Listener performance Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "MDB Vs  Message Listener performance " Watch "MDB Vs  Message Listener performance " New topic
Author

MDB Vs Message Listener performance

kri shan
Ranch Hand

Joined: Apr 08, 2004
Posts: 1372
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

Joined: Apr 08, 2004
Posts: 1372
Any update ?
kri shan
Ranch Hand

Joined: Apr 08, 2004
Posts: 1372
reply ?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: MDB Vs Message Listener performance
 
Similar Threads
Who creates destination Queueor Topic
Message Driven Beans
Doubts on MDB's
why not durable subscriber on queue, and more?
Message Facade (Message Driven Bean)