Bharath Ganesh wrote: > Personally, I don't thing the EJB container should default the MDB > pool size to unlimited. The EJB container would be completely > agnostic of the message broker configuration(maxSessions in case of > ActiveMQ) and would need the throttle to be setup itself, without > assuming the provider configuration.
My question is why the ejb container needs to assume that it has to limit the instances by default? Apart from resource management being a big deal in JEE in general. I agree completely that the ejb container should be agnostic of intimate knowledge of the resource adapter. You've certainly got a point there. But isn't it rather safe to assume that the ra has a legitimate reason for requesting a new endpoint when it does? Even if that happens to be the eleventh one for a particular MDB? Disregarding the case when a rouge ra starves the system, is anyone aware of a ra implementation that as a default will continue requesting endpoints for a MDB until it gets a UnavailableException? Obviously I recognize that I'm not intimate with all the details of JEE yet, so it could very well be a legitimate design pattern. -- Fredrik Jonson
