The JMSContainerInvoker holds (and could expose via JMX) the container-configuration.container-pool-conf.maximumsize setting correct? Does the JMSContainerInvoker also store the proxy-binding.proxy-factory-config.maximumsize as well? The proxy-binding is the one I'm more interested in being able to tweak at runtime, not necessary the container-configuration since I could turn strict sizing off and let it grow dynamically in the cases where the proxy-binding maximumsize would be changed to be larger then the container-configuration-pool maximumsize. Or am I incorrect?
Dustin > -----Original Message----- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Friday, February 06, 2004 9:25 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Changing a proxy-binding/container-config at > runtime > > > On Fri, 2004-02-06 at 13:53, Barlow, Dustin wrote: > > Is there a way to change the MaximumSize settings on both > the proxy-binding > > and the container-config at runtime? I hunted around the > JMX console to see > > if there were any administrative methods exposed to do > this, but I didn't > > find any. > > > > I want to be able to throttle the load on a system via the > number of MDBs > > that can fire in parallel. I want it to be tweakable thru a web > > administration console. Is this possible? > > > > It is possible, but it is not currently exposed via JMX. > You could modify (or extend) JMSContainerInvoker to expose > "maxPoolSize" as a JMX attribute. The JMSContainerInvoker > is exposed as an MBean in the jboss.j2ee domain. > > To make it take affect you would need to pass the change onto the > ServerSessionPool. But this standard interface does not expose > a setMaxPoolSize() method. For JBoss's implementation at least, > it uses a PooledExecutor which does allow the pool size to be modified > at runtime. But in general we allow you choose which session pool > implementation to use which might not have this behaviour. > > An alternate (more portable) approach would be to allow the > pool size to > be modified via jmx, but use stop/startDelivery to recreate the pool > with the new size. > > Regards, > Adrian > > > Thanks, > > Dustin > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > -- > xxxxxxxxxxxxxxxxxxxxxxxx > Adrian Brock > Director of Support > Back Office > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
