Brock [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 06, 2004 10:59 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] Changing a proxy-binding/container-config at
> run time
>
>
> On Fri, 2004-02-06 at 15:53, Barlow, Dustin wrote:
> > The JMSContainerInvoker ho
On Fri, 2004-02-06 at 15:53, Barlow, Dustin wrote:
> 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 p
Yes,
You can simply add:
/**
* @jmx:managed-attribute
*/
public int getMaxPoolSize()
{
return maxPoolSize;
}
/**
* @jmx:managed-attribute
*/
public void setMaxPoolSize(int maxPoolSize)
{
this.maxPoolSize = maxPoolSize;
}
I just committed this
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 t
Thanks for the information. Is exposing the MaximumSize via JMX in the
JMSContainerInvoker something that could be added to the canonical source
tree? Seems to me that others could use this basic functionality as well.
I am a little leary of forking my own version simply because it's just
another
