Hide Forgot
Description of problem: The feature request is to have a priority configured on a gateway and then have that propagate through the ESB services which are invoked as a result. The priority should be applied to any JMS transports which are used to communicate with ESB services, using the JMS message setJMSPriorty, and propagated through those services to subsequent ESB service invocations. Expected results: JMS priority can be used by reorder messages arriving at JMS endpoints so that certain services can take precedence over lower priority services. Additional info: I have a good idea of how this can be addressed.
Just to confirm - does JBossESB have to do anything with this priority, other than define it for a gateway and propagate it in the messages that pass through that gateway?
Question are JBossESB editor/tooling changes needed?
(In reply to comment #1) > Just to confirm - does JBossESB have to do anything with this priority, other > than define it for a gateway and propagate it in the messages that pass through > that gateway? The priority needs to be applied to each JMS message sent, directly or indirectly, as a result of the incoming messages at the gateway.
(In reply to comment #2) > Question are JBossESB editor/tooling changes needed? No editor/tooling changes are being requested at this time, only server side.
So: '...The priority needs to be applied to each JMS message sent, directly or indirectly, as a result of the incoming messages at the gateway...' The ESB will also be throttling throughput based on message priority?
(In reply to comment #5) > The ESB will also be throttling throughput based on message priority? The ESB will do nothing more than consume messages as they are provided by the JMS provider; the JMS providers should be delivering the messages based on the JMS priority. The JMS API defines 10 priority levels 0 (lowest) - 9 (highest). The default level is 4.
Functionality added in ESB through JBESB-3786
Documented.
I am using SOA Platform 5.3 ER3. In this version it seems that the functionality is not there. After investigating futher I have come to conclusion that the functionality wasn't productized into this version of SOA Platform because I do not see the changes from branch JBESB_4_11_CP@38100 in jboss-rosetta.jar (e.g. new class MessageFlowContext.java is not there)
JIRA https://issues.jboss.org/browse/JBESB-3786 states that it should be possible to set it on listener/bus/provider. I couldn't set it on a bus nor provider. The esb fails to deploy with validation error: 10:44:29,529 INFO [org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment] Starting ESB Deployment 'JmsPriority.esb' 10:44:29,531 ERROR [org.jboss.soa.esb.listeners.config.model.ModelParser$XmlErrorHandler] ERROR-null-26:cvc-complex-type.2.4.d: Invalid content was found starting with element 'property'. No child element is expected at this point.
Likely caused by having the property element in the wrong place. Using the helloworld quickstart as an example, this is how it could be configured <jms-provider name="JBossMQ" connection-factory="ConnectionFactory"> ===> <property name="messageFlowPriority" value="4"/> <jms-bus busid="quickstartGwChannel"> ===> <property name="messageFlowPriority" value="4"/> <jms-message-filter dest-type="QUEUE" dest-name="queue/quickstart_helloworld_Request_gw" /> </jms-bus> ... <jms-listener name="JMS-Gateway" busidref="quickstartGwChannel" is-gateway="true"> ===> <property name="messageFlowPriority" value="4"/> </jms-listener>
Yes you are right Kevin. I have placed the property elements after to the end of the jms-provider element and to the end of the jms-bus element which gives a validation error.
Employee 'fnguyen' has left the company.