David Blevins wrote: > 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.
ActiveMQ has the default value for maxSessions set to 10. http://activemq.apache.org/activation-spec-properties.html Unfortunately 'maxSessions' is a activation property that is specific to ActiveMQ. As far as my limited reading of the jms spec now reach - I've not found a standard way of specifying the number of instances to create. On the other hand, I'd be willing to bet that all major JMS resource adapters implement a activation property for this. ActiveMQ has the maxSessions which defaults to 10, and OpenMQ has a EndpointPoolMaxSize which defaults to 15. > Not sure how we'd actually implement that in Geronimo -- i.e. > detecting which resource adapter implementation is being used. I'd avoid that route as it requires intimate knowledge of the resource adapters. If openejb make a special case of ActiveMQ my original use case, a custom resource adapter, would still be exposed to the default instance limit. Perhaps it would be possible to make the instance limit configurable per MDB in openejb-jar.xml? I'm not sure when the MdbInstanceFactory is created, but if it is created on demand when openejb-jar.xml is parsed that would be a possibility. Maybe the right thing to do is for G to set up a server-jar.xml of their own, that overrides the default instance limit, instead of using the default server-jar.xml that is included in openejb-core.jar? -- Fredrik Jonson
