[Bug 56510] JMS Publisher: Enable proper usage of JMS properties for priority and expiry of a message

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=56510

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
           Severity|normal                      |enhancement

--- Comment #2 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Thanks for patch.
First I requalify this as an enhancement, as currently JMeter does not handle
those 2 Headers.

Regarding patch, I think integrating it as-is would be a bit disturbing as the
2 "properties" are in fact Headers, so allowing users to put them in JMS
Properties would be misleading.

According to:
http://docs.oracle.com/javaee/1.4/tutorial/doc/JMS4.html#wp79367

I understand we are not able to set those:
- JMSExpiration
- JMSPriority

Others being set through different ways in JMeter, by broker, or automatically.

I think to be clear, we should introduce 2 custom fields in GUI between timeout
and delivery as there is place and it makes sense there.

Tell me if you could rework your patch, if not I will do .

Thanks for contribution.

-- 
You are receiving this mail because:
You are the assignee for the bug.