Win a copy of Spring in Action (5th edition) this week in the Spring forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Ganesh Patekar
  • Frits Walraven
  • Tim Moores
  • Ron McLeod
  • Carey Brown
Bartenders:
  • Stephan van Hulst
  • salvin francis
  • Tim Holloway

EJB MDB doubt  RSS feed

 
Ranch Hand
Posts: 114
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

The container serializes calls to each message-driven bean instance. Most containers will
support many instances of a message-driven bean executing concurrently; however, each
instance sees only a serialized sequence of method calls. Therefore, a message-driven bean
DOES NOT have to be coded as reentrant.


what does it mean when said

MDBs should not be coded as reentrant

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"reentrant" means a multi-threaded environment where a method can be executed concurrently by different threads. This is not applicable to MDBs as everytime a message listener method is executed (or a timer callback) a new instance is picked up by the container from the pool.

Hope this answers.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!