You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/06/03 05:04:07 UTC

[jira] Commented: (QPID-1887) JMS TTL not working

    [ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715782#action_12715782 ] 

Rajith Attapattu commented on QPID-1887:
----------------------------------------

A fix for this has been committed at rev 781141 in Qpid trunk.

> JMS TTL not working
> -------------------
>
>                 Key: QPID-1887
>                 URL: https://issues.apache.org/jira/browse/QPID-1887
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M4
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.6
>
>
> Even ff ttl is set in the message producer, it does not get set properly in the
> message properties. Hence the broker is not expiring them. 
> In the 0-10 codepath, the JMS client was incorrectly setting the expiration field instead of the ttl field.
> This is also related to QPID-1575

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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org