You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dave Thompson (JIRA)" <ji...@apache.org> on 2012/05/27 13:58:23 UTC
[jira] [Created] (AMQ-3862) Ajax / REST connector doesn't support
guaranteed delivery
Dave Thompson created AMQ-3862:
----------------------------------
Summary: Ajax / REST connector doesn't support guaranteed delivery
Key: AMQ-3862
URL: https://issues.apache.org/jira/browse/AMQ-3862
Project: ActiveMQ
Issue Type: Bug
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3862) Ajax connector doesn't support
guaranteed delivery
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated AMQ-3862:
-----------------------------
Issue Type: Improvement (was: Bug)
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3862) Ajax connector doesn't support
guaranteed delivery
Posted by "Dave Thompson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Thompson updated AMQ-3862:
-------------------------------
Summary: Ajax connector doesn't support guaranteed delivery (was: Ajax / REST connector doesn't support guaranteed delivery)
> Ajax connector doesn't support guaranteed delivery
> --------------------------------------------------
>
> Key: AMQ-3862
> URL: https://issues.apache.org/jira/browse/AMQ-3862
> Project: ActiveMQ
> Issue Type: Bug
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira