You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2007/04/12 14:30:34 UTC

[jira] Created: (AMQ-1227) ActiveMQ web component - proper handling of priority, timeToLive and delivery mode

ActiveMQ web component - proper handling of priority, timeToLive and delivery mode
----------------------------------------------------------------------------------

                 Key: AMQ-1227
                 URL: https://issues.apache.org/activemq/browse/AMQ-1227
             Project: ActiveMQ
          Issue Type: Improvement
    Affects Versions: incubation
            Reporter: Dejan Bosanac
             Fix For: incubation
         Attachments: activemq-web.patch

Currently, web component does not handle priority, time to live and delivery mode properties when sending messages as it should. All messages are sent as  non-persistant, with time to expire set to 0 and priority 4.
Submitted patch fixes some of the spotted problems. It checks for JMSPriority, JMSTimeToLIve and JMSDeliveryMode request parameters and acts according to their values. If they are not set it uses default values (priority =5, delivery mode = persistent, no expiry time).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AMQ-1227) ActiveMQ web component - proper handling of priority, timeToLive and delivery mode

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39481 ] 

Dejan Bosanac commented on AMQ-1227:
------------------------------------

Thanks James. That's great.

> ActiveMQ web component - proper handling of priority, timeToLive and delivery mode
> ----------------------------------------------------------------------------------
>
>                 Key: AMQ-1227
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1227
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: incubation
>            Reporter: Dejan Bosanac
>             Fix For: 5.0.0
>
>         Attachments: activemq-web.patch
>
>
> Currently, web component does not handle priority, time to live and delivery mode properties when sending messages as it should. All messages are sent as  non-persistant, with time to expire set to 0 and priority 4.
> Submitted patch fixes some of the spotted problems. It checks for JMSPriority, JMSTimeToLIve and JMSDeliveryMode request parameters and acts according to their values. If they are not set it uses default values (priority =5, delivery mode = persistent, no expiry time).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQ-1227) ActiveMQ web component - proper handling of priority, timeToLive and delivery mode

Posted by "James Strachan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan resolved AMQ-1227.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: incubation)
                   5.0.0

Patch applied with thanks! Incidentally I've added you to the contributor page; feel free to add your company affiliation: http://cwiki.apache.org/confluence/display/ACTIVEMQ/Team

> ActiveMQ web component - proper handling of priority, timeToLive and delivery mode
> ----------------------------------------------------------------------------------
>
>                 Key: AMQ-1227
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1227
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: incubation
>            Reporter: Dejan Bosanac
>             Fix For: 5.0.0
>
>         Attachments: activemq-web.patch
>
>
> Currently, web component does not handle priority, time to live and delivery mode properties when sending messages as it should. All messages are sent as  non-persistant, with time to expire set to 0 and priority 4.
> Submitted patch fixes some of the spotted problems. It checks for JMSPriority, JMSTimeToLIve and JMSDeliveryMode request parameters and acts according to their values. If they are not set it uses default values (priority =5, delivery mode = persistent, no expiry time).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.