summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Sackman <matthew@rabbitmq.com>2010-12-09 17:01:06 +0000
committerMatthew Sackman <matthew@rabbitmq.com>2010-12-09 17:01:06 +0000
commit5b57841b188c8427b4ffa32df1e52607516e1ba7 (patch)
tree11f1415d6cf8a678ec6d6bf1dd696ce7006ea8e1
parent6a1af9f1b5330b606f690a848fda821f26720f55 (diff)
downloadrabbitmq-server-git-5b57841b188c8427b4ffa32df1e52607516e1ba7.tar.gz
Turns out the memory_monitor and fhc callback registration is idempotent, and it's also just simply easier to correctly fake the amqqueue_process API. Need to then deal with rate timers and pre hibernation callbacks. Groan
-rw-r--r--src/rabbit_amqqueue_process.erl4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/rabbit_amqqueue_process.erl b/src/rabbit_amqqueue_process.erl
index 027a82e7db..4985643122 100644
--- a/src/rabbit_amqqueue_process.erl
+++ b/src/rabbit_amqqueue_process.erl
@@ -138,10 +138,6 @@ init(Q) ->
init_with_backing_queue_state(Q, BQ, BQS) ->
?LOGDEBUG("Queue starting - ~p~n", [Q]),
process_flag(trap_exit, true),
- ok = file_handle_cache:register_callback(
- rabbit_amqqueue, set_maximum_since_use, [self()]),
- ok = rabbit_memory_monitor:register(
- self(), {rabbit_amqqueue, set_ram_duration_target, [self()]}),
process_args(#q{q = Q#amqqueue{pid = self()},
exclusive_consumer = none,
has_had_consumers = false,