Pooling concept in java or EJB? -


we have pooling concept in stateless ejb. advantage of using pooling? understanding save time in object creation. right? if yes, there significant difference in performance in creating object or getting existing pool? pooling serve other purpose this?

pooling can usefull sharing limited resources (e.g. database connections) , re-using objects expensive create and/or destroy. when combined ejb, can limit load on overall system usefull when run server. according accepted answer in similar question, helps thread-safety.

an ejb can expensive create (or setup) when various resources , other ejb's injected (with annotations), which, in experience, common case. however, appears example jboss repeats process pooled ejbs (see answer tom anderson in similar question).

if common ejb in pool injected in other ejbs, other ejbs have wait common ejb become available when system busy. common ejb in pool acting shared limited resource. drawback can time-out exceptions (after example 50 seconds) @ unexpected places when common ejb not available (sometimes caused hickup in infrastructure).

i have experience jboss server has pool mechanism stateless ejbs in place. within jboss server there common ejb uses database connection frequently. if huge amount of work enters system @ once, load high limited pooling mechanism. if pooling mechanism limits maximum load much, maximum load can increased increasing maximum pool size.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -