On Apr 8, 2009, at 12:56 AM, Fredrik Jonson wrote:
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.
To me this seems like the most promising approach. At least on this
project we don't have an aversion to having enhanced support for
pluggable things so that users have less work. We support the various
'give me your transaction manager' properties that all JPA
implementations seem to have:
hibernate.transaction.manager_lookup_class, toplink.target-server,
eclipselink.target-server, etc.
But really maybe what we need is an @PoolSize annotation so people
could set the value on their MDB class right next to the
@ActivationConfig. Then both would be set in the same place and just
might make things easier all around.
-David
