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)" <ji...@apache.org> on 2010/10/18 18:35:23 UTC
[jira] Updated: (QPID-2350) Have a consistent mechanism for
handling heartbeats in Java client
[ https://issues.apache.org/jira/browse/QPID-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-2350:
-----------------------------------
Fix Version/s: (was: 0.7)
0.9
Moving the fix version to 0.9
Currently the client (0-10 code path) handles both the new and old property names and if the old prop name is used, it prints a warning that the old name is deprecated.
The new property is qpid.heartbeat and is given in secs.
Once QPID-2343 is completed this property could leverage the same mechanism to handle the above.
> Have a consistent mechanism for handling heartbeats in Java client
> ------------------------------------------------------------------
>
> Key: QPID-2350
> URL: https://issues.apache.org/jira/browse/QPID-2350
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.9
>
>
> Currently the JMS Client has two different properties for handling heartbeats in 0-10 and 0-8/0-9 clients.
> One property is in secs, while the other is in milisecs.
> This has led to misunderstanding and a few users have complained about this.
> QPID-2343 introduces a mechanism to provide a consistent naming convention while supporting old prop names.
> This JIRA hopes to leverage that mechanism to fix this issue.
--
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