Support TPS controlling for JMS inbound endpoint

[Drifftr]

Description:
According to the current architecture when a inbound endpoint poll happens it tries to receive all the messages produced for the particular consumer[1]. We don't have any control over the number of messages should be picked up in each poll. Its better to have this as an option since some users may need this to use in a controlled TPS level.

[1]. https://github.com/wso2/carbon-mediation/blob/master/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint/src/main/java/org/wso2/carbon/inbound/endpoint/protocol/jms/JMSPollingConsumer.java#L283

Suggested Labels:

Suggested Assignees:

Affected Product Version:
EI 6.1.1

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

[jpbelangerfromquebec]

I agree that this is something major. We must be able to perform some kind of throttling.

[v-scottbechtel]

Does this apply to EI 6.6.0 as well?