You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/04/08 22:05:25 UTC
[jira] [Closed] (AMQ-3862) Ajax connector doesn't support
guaranteed delivery
[ https://issues.apache.org/jira/browse/AMQ-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3862.
-----------------------------
Resolution: Won't Fix
> Ajax connector doesn't support guaranteed delivery
> --------------------------------------------------
>
> Key: AMQ-3862
> URL: https://issues.apache.org/jira/browse/AMQ-3862
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.6.0
> Environment: Windows 7
> Reporter: Dave Thompson
>
> The Ajax connector do not support guaranteed delivery. As each message is sent without a unique identifier and there is no checking of this, then it is possible for a transport-level issue to cause messages to be lost.
> A good way to fix this would be to hold a queue of dispatched messages inside the servlets, and the Ajax client could then submit the last received message ID when it commences the poll for new messages - and the queued items which have been delivered could then be erased.
> I'd try and fix this myself but I can't get the trunk working in Eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)