yes, there are two entries where you may configure this. And this also confused me;
see my thread
But from the answers I got in the forums the correct place is
<invoker-proxy-binding> <name>message-driven-bean</name> <invoker-mbean>default</invoker-mbean> <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> <proxy-factory-config> ... </proxy-factory-config> </invoker-proxy-binding>
Here please configure MaximumSize to 1. See the JBoss 3.2.2 book:
For the JMS specific proxy factory, org.jboss.ejb.plugins.jms.JMSContainerInvoker, there is an MDBConfig "MaximumSize: This specifies the upper limit to the number of concurrent MDBs that will be allowed for the JMS destination associated with a given MDB deployment. This defaults to 15.
The container configuration of the MDB is tied by the name "message-driven-bean" to this invoker.
The descriptions of the DTDs in
is IMHO somewhat misleading:
The capacity of the Pool. For pools where reclaim is possible, the pool will also be repopulated when the instance is free to be reused. This is not an hard limit, if instances are needed when the pool is at its MaximumSize, new instances will be created following the demand unless a strictMaximumSize of true is specified. Used in: container-pool-conf and invoker-proxy-conf for JMSContainerInvoker
The strictMaximumSize is not applicable here.
You can also make this configuration local to your MDB by supplying an own container-configuration in you META-INF/jboss.xml file.
Please post if this give the expected results. I am still a little bit unsure about this.
it worked. thanks a lot for the quick reply.
would you like to try it as a per container config?