Follow-up to PR #1332

Even though we do not use the AMQP xml spec files, they should be updated Related to #1336
rabbitmq · Apr 10, 2023 · 9da0f51 · 9da0f51
1 parent b8ab497
commit 9da0f51
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/projects/specs/amqp0-9-1.stripped.xml b/projects/specs/amqp0-9-1.stripped.xml
@@ -34,6 +34,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   <constant name="frame-end" value="206"/>
   <constant name="reply-success" value="200"/>
   <constant name="content-too-large" value="311" class="soft-error"/>
+  <constant name="no-route" value="312" class="soft-error"/>
   <constant name="no-consumers" value="313" class="soft-error"/>
   <constant name="connection-forced" value="320" class="hard-error"/>
   <constant name="invalid-path" value="402" class="hard-error"/>

diff --git a/projects/specs/amqp0-9-1.xml b/projects/specs/amqp0-9-1.xml
@@ -187,6 +187,13 @@
     </doc>
   </constant>
 
+  <constant name = "no-route" value = "312" class = "soft-error">
+    <doc>
+      Returned when RabbitMQ sends 'basic.return' when a 'mandatory'
+      message cannot be delivered to any queue.
+    </doc>
+  </constant>
+
   <constant name = "no-consumers" value = "313" class = "soft-error">
     <doc>
       When the exchange cannot deliver to a consumer when the immediate flag is