I also have a requirement to limit a certain MDB to a maximum of one instance, but I am a bit confused as to your response. Are you saying that I should put a pool size limit on the <outbound-resourceadapter> which defines the Connection Factory that my MDB subscribes to?
Thanks, Aman djencks wrote: > > > It might possibly work for activemq if you don't use any > transactions, but if you use transactions I would expect it to > completely break and give pretty random behavior. I don't think > there's any reason to expect it to work even without transactions. > > I have trouble keeping all the places you can configure sizes > straight, but one way to limit the number of active mdbs is to give > the inbound resource adapter its own thread pool and limit that > size. I think there's a more direct way but don't recall what it is. > > If the number of outbound connections is at least the number of mdbs > I would expect you wouldn't run into problems. > > Maybe someone with more actual experience can give some more informed > advice. > > thanks > david jencks > >> >> >> > > > -- View this message in context: http://www.nabble.com/Sharing-resources-in-an-MDB-tf3412013s134.html#a10182882 Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
