[
https://issues.apache.org/activemq/browse/SM-521?page=comments#action_36735 ]
Guillaume Nodet commented on SM-521:
------------------------------------
I'd like non lightweight components to be able to have throttling properties
configured as well.
In xbean, the <sm:component> tag only identifies the "component" property of
the enclosing ActivationSpec,
so you can not put attributes on this tag.
These properties are also specific to ServiceMix container and really
independant of the component itself.
They are used on the DevlieryChannel for the component, but the component has
really no control on them.
I think these parameters should be on the activationSpec.
<sm:activationSpec throttlingTimeout="500" throttlingInterval="5">
<sm:component> ...
For standard JBI components deployed using std JBI packaging, we need to define
some abstract activationSpec.
<sm:activationSpec componentName="servicemix-http" throttlingTimeout="500"
throttlingInterval="5" />
without any component defined.
When a component is installed using the hot deploy dir or ant tasks / jmx, the
container would look for a registered
activationSpec with the same component name and use these values to configure
the ComponentMBeanImpl and / or
DeliveryChannelImpl.
Furthermore, I think these properties should be the default value. If someone
configure these properties using
jms (as it is already possible), these properties should be persisted
somewhere. It could be in the status file associated with the component (see
ComponentMBeanImpl.stateFile).
These values should override any value set in the activationSpec.
Thus, there is no need for components to inherit a servicemix specific class,
as these properties are controlled
by the jbi container itself, and not used at all by the components
the component, maybe
> Tuning parameters configuration
> -------------------------------
>
> Key: SM-521
> URL: https://issues.apache.org/activemq/browse/SM-521
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-core
> Reporter: Guillaume Nodet
> Fix For: 3.0-M3
>
>
> We need to provide a way to configure tuning parameters for servicemix:
> * thread pools (core + flows + seda queues + components )
> * queues (delivery channels + seda queues)
> * component throttling
> This may need a way to configure dummy activationSpecs (with no components,
> only the component name)
> so that we can configure these parameters when using JBI std installation
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
