qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7648) [Java Broker] Reject AMQP 1.0 durable messages if no persistent store is configured
Date Tue, 09 May 2017 11:01:04 GMT

    [ https://issues.apache.org/jira/browse/QPID-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002486#comment-16002486

Keith Wall commented on QPID-7648:

I think the protocol layer should ask the store if it is capable of fulfilling the obligation
and the protocol layer should respond accordingly.  Stores like BDB, Derby and JDBC will always
return true.  The MemoryMessageStore should default to return false, but this should be overridable
for test purposes.

> [Java Broker] Reject AMQP 1.0 durable messages if no persistent store is configured
> -----------------------------------------------------------------------------------
>                 Key: QPID-7648
>                 URL: https://issues.apache.org/jira/browse/QPID-7648
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Lorenz Quack
>             Fix For: qpid-java-broker-7.0.0
> AMQP 1.0 specifies in 3.2.1 that
> bq. Durable messages MUST NOT be lost even if an intermediary is unexpectedly terminated
and restarted. A target which is not capable of fulfilling this guarantee MUST NOT accept
messages where the durable header is set to true: if the source allows the rejected outcome
then the message SHOULD be rejected with the precondition-failed error, otherwise the link
MUST be detached by the receiver with the same error.
> I do not think we are currently doing that.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message