[ https://issues.apache.org/jira/browse/QPID-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Vavricka updated QPID-7815: --------------------------------- Attachment: 0001-QPID-7815-Reject-policy-type.patch Hi, implemented review comments, only the dependency in pom.xml is still there because I use {{JmsConnection}} in {{QueuePolicyTest#testRejectPolicy}} to distinguish between type of connection (AMQP 1.0 or AMQP 0-10 and older). The distinguish is there because AMQP 1.0 exception doesn't have error code set. When dependency is missing code doesn't compile for other profiles than {{java-mms.1-0}}. Test {{QueuePolicyTest#testRejectPolicy}} is fixed without closing connection. For AMQP 1.0 I used error {{TransactionErrors.TRANSACTION_ROLLBACK}} instead of {{AmqpError.RESOURCE_LIMIT_EXCEEDED}}. AMQP 0-10, 0-9-1, 0-9, 0-8 uses {{ErrorCodes.RESOURCE_ERROR}}. > Reject policy type > ------------------ > > Key: QPID-7815 > URL: https://issues.apache.org/jira/browse/QPID-7815 > Project: Qpid > Issue Type: New Feature > Components: Java Broker > Affects Versions: qpid-java-broker-7.0.0 > Reporter: Tomas Vavricka > Assignee: Lorenz Quack > Labels: policy-type, queue, reject > Fix For: qpid-java-broker-7.0.0 > > Attachments: > 0001-QPID-7815-Java-Broker-Enable-QueuePolicyTests-on-all.patch, > 0001-QPID-7815-Reject-policy-type.patch > > > It would be good if Java Broker will support reject policy. > Reject policy - reject incoming message(s) when queue capacity is reached > Queue capacity can be defined by maximum count of message and maximum size of > messages (including header). -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org