So you're wait is really on the mdb pool not the session pool. The session pool wait is still there.
You probably still have the default 15 sessions in the pool? Under load, this will mean you have 1 session delivering its message and 14 waiting for the single instance mdb. Each of those 14 sessions will have a message attached. Regards, Adrian On Thu, 2003-08-14 at 21:13, Barlow, Dustin wrote: > In conf/standardjboss.xml I setup a new invoker-proxy-binding and a > container-configuration. Part of the container-configuration includes the > following stanzas: > > <container-pool-conf> > <MaximumSize>1</MaximumSize> > <MinimumSize>1</MinimumSize> > <strictMaximumSize>true</strictMaximumSize> > </container-pool-conf> > > The MDB is deployed using the new invoker-proxy-binding and > container-configuration and does only consume one message at a time as long > as there isn't a container transaction rollback. > > BTW: I'm using JBoss 3.2.2RC2. > > Dustin > > -----Original Message----- > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Sent: 8/14/2003 2:27 PM > Subject: RE: [JBoss-user] MDB Singleton retry semantics > > How are you enforcing the singleton? -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
