[jboss-user] [EJB3] - Re: EJB3 Session Bean Pool

Carlo de Wolf [http://community.jboss.org/people/wolfc] created the discussion "Re: EJB3 Session Bean Pool" To view the discussion, visit: http://community.jboss.org/message/599127#599127 -------------------------------------------------------------- Hi Robert, Glad to see you're making good progress. There is an unwritten rule that the Pool should remove its pooled instances whenever it is destroyed. StrictMaxPool doesn't follow this yet. The Pool itself gets destroyed on undeploy or shutdown. In essence it means that the application will be tidied up a bit cleaner. A Pool is called concurrently and thus thread safety must be implemented manually. Each synchronized block / method is a bottleneck for all incoming calls and should be kept to a minimum. Also because synchronized is an unfair lock on the pool, it leads to a high deviation in response times. ThreadlocalPool for example has the objective to keep thread locking to a minumum, thus giving the best throughput. Based on a pools requirements a choice must be made for modifying shared data: atomic, unfair lock or fair lock. The counts in JBoss AS 4 are wrongly implemented and this was fixed. (See https://issues.jboss.org/browse/EJBTHREE-2155 https://issues.jboss.org/browse/EJBTHREE-2155.) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/599127#599127] Start a new discussion in EJB3 at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]