You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2011/08/11 18:27:27 UTC

[jira] [Commented] (APLO-72) client-individual ack mode is not supported

    [ https://issues.apache.org/jira/browse/APLO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083208#comment-13083208 ] 

Hiram Chirino commented on APLO-72:
-----------------------------------

Yep. we have the wrong constants (this was implemented before 1.1 solidified).  We should be using the stomp 1.1 defined header names.

> client-individual ack mode is not supported
> -------------------------------------------
>
>                 Key: APLO-72
>                 URL: https://issues.apache.org/jira/browse/APLO-72
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>            Reporter: Lionel Cons
>
> The current Apollo snapshot does not support the client-individual ack mode although it is mentioned in the user manual, in the "Reliable Messaging" section.
> FWIW, it is also defined in the STOMP 1.1 spec.
> Using it, we get: "Unsuported ack mode: client-individual". (yes, there is a typo here...)
> More confusing, the code contains other ack modes which are not documented:
>   val ACK_MODE = ascii("ack")
>   val ACK_MODE_AUTO = ascii("auto")
>   val ACK_MODE_NONE = ascii("none")
>   val ACK_MODE_CLIENT = ascii("client")
>   val ACK_MODE_SESSION = ascii("session")
>   val ACK_MODE_MESSAGE = ascii("message")
> Could client-individual be supported and all ack modes documented please?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira