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/02 21:09:07 UTC
[jira] Created: (QPID-1887) JMS TTL not working
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
[jira] Commented: (QPID-1887) JMS TTL not working
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Commented: (QPID-1887) JMS TTL not working
Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715933#action_12715933 ]
Rafael H. Schloming commented on QPID-1887:
-------------------------------------------
Shouldn't the code that sets the ttl be moved outside the if (!_disableTimestamps) {...} block?
> 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
[jira] Commented: (QPID-1887) JMS TTL not working
Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715939#action_12715939 ]
Rafael H. Schloming commented on QPID-1887:
-------------------------------------------
Also, according to the JMS javadoc, we need to set the expiration based on the ttl and current time, so we shouldn't remove the code that does that.
> 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
[jira] Resolved: (QPID-1887) JMS TTL not working
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-1887.
---------------------------------
Resolution: Fixed
> 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
[jira] Updated: (QPID-1887) JMS TTL not working
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-1887:
-----------------------------------
Status: Ready To Review (was: In Progress)
> 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