summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2012-01-25 15:17:48 +0000
committerSimon MacMullen <simon@rabbitmq.com>2012-01-25 15:17:48 +0000
commitf5ac6ad4dbc667b88c5da578b509404bbc5b9b26 (patch)
treeae27e61c8dff00c144efea2d931113289b8e8107 /src
parenta9672d08ef959969e698310e81e4b18e5b19204a (diff)
downloadrabbitmq-server-git-f5ac6ad4dbc667b88c5da578b509404bbc5b9b26.tar.gz
I think this should be a soft error. Although the spec does say to use command-invalid when the client attempts to declare an exchange of an unknown type, that's much more obviously the client's fault. So let's go with an old favourite.
Diffstat (limited to 'src')
-rw-r--r--src/rabbit_exchange_type_invalid.erl2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/rabbit_exchange_type_invalid.erl b/src/rabbit_exchange_type_invalid.erl
index fc589450cf..8f60f7d898 100644
--- a/src/rabbit_exchange_type_invalid.erl
+++ b/src/rabbit_exchange_type_invalid.erl
@@ -34,7 +34,7 @@ serialise_events() -> false.
route(#exchange{name = Name, type = Type}, _) ->
rabbit_misc:protocol_error(
- command_invalid,
+ precondition_failed,
"Cannot route message through ~s: exchange type ~s not found",
[rabbit_misc:rs(Name), Type]).