I wonder if there's some sneaky way we can get the maxSessions number
from ActiveMQ and set the pool size to be the same: or alternatively
setting it to unlimited if activemq is the resource adapter, though I
hope there is no equivalent 'unlimited' setting for the maxSessions.
Not sure how we'd actually implement that in Geronimo -- i.e.
detecting which resource adapter implementation is being used.
David Jencks, any ideas?
-David
On Apr 7, 2009, at 4:06 AM, 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.
Any thoughts?
On Tue, Apr 7, 2009 at 2:50 PM, Fredrik Jonson
<fred...@myrealbox.com>wrote:
Hi,
I've run into a problem changing the instance limit in Geronimo[0]
and
while looking into that I wonder, isn't the default instance limit of
10 for MDBs pretty arbitrary set?
What are the consequences if the default is changed to 0
(unlimited)? If
I understand correctly, the prominent use case is ActiveMQ, and they
already
control the number of concurrent instances with the maxSessions
parameter.
I saw a previous discussion[1] a year ago that seems to end in
nothing. If
there are no technical objections I'd like to open a jira issue for
this.
[0] http://thread.gmane.org/gmane.comp.java.geronimo.user/12800
[1] http://thread.gmane.org/gmane.comp.java.openejb.devel/7444
--
Fredrik Jonson
