Not really, this is not 1-1 ejb pool is hidden so you can get 5 and 10 IMO Le 14 nov. 2013 20:11, "um" <[email protected]> a écrit :
> How would the following work? > > wmqra activation spec specifies maxPoolDepth as follows (in ejb-jar) > > <activation-config-property> > > > <activation-config-property-name>maxPoolDepth</activation-config-property-name> > > <activation-config-property-value>5</activation-config-property-value> > </activation-config-property> > > tomee.xml has the following - > instanceLimit=10 > > I am expecting that there would be 5 instances of the MDB based on > maxPoolDepth > > This is my understanding from what you have said - the container provides > the resource adapter with the factory for creation of message endpoint > instances. When a message arrives, the resource adapter determines the MDB > and using the MesageEndpointFactory creates an MDB instance by invoking > the > endpoint creation methods on the factory. But what makes the decision of > creating new instance as opposed to using existing one. What makes the > decision to remove the instance after every onMessage()? > > Thanks > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/MDB-being-instantiated-on-every-message-tp4665830p4666181.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
