summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Two modes for delete, one for when the server is running and we need to be ↵bug26347Simon MacMullen2014-08-153-40/+53
| | | | quick going via the reverse route, and another when it is down and we need to clean up durable routes. Not entirely happy with the elegance of this but it gets the tests to pass.
* Merge bug26341Simon MacMullen2014-08-131-3/+2
|\
| * BE more assertive.bug26341Simon MacMullen2014-08-131-3/+2
|/
* Merge bug26338Simon MacMullen2014-08-120-0/+0
|\
* | Catch enotconn here.bug26338Simon MacMullen2014-08-121-1/+1
|/
* Added tag rabbitmq_v3_3_5 for changeset 3347a7f0e689Simon MacMullen2014-08-110-0/+0
|
* Changelogs for 3.3.5.rabbitmq_v3_3_5Simon MacMullen2014-08-112-0/+10
|
* Merge bug26313 (again)Simon MacMullen2014-08-115-1/+108
|\
| * Fix typo spotted by Edwin Fine.Simon MacMullen2014-08-081-1/+1
| | | | | | | | Since hitting this line would cause a crash in the caller, and since this code is used very heavily (e.g. in the gen_server2 prioritised mailbox) and since it's been like that for over a year, I can only conclude that this code is unreachable. That conclusion is backed up by trying to get a pqueue() into a state which would hit that head - I was not able to. Still, it should be fixed...
| * Tweak timings, shorten name, explain heuristics, specify which process info ↵Simon MacMullen2014-08-071-10/+21
| | | | | | | | items we want (especially to add 'monitors' and remove 'messages').
| * Merge bug 26322Simon MacMullen2014-08-061-0/+8
| |\
| | * Add loopback_users (somewhat late...)bug26322Simon MacMullen2014-08-061-0/+8
| |/
| * Merge bug26301Simon MacMullen2014-08-062-0/+20
| |\
| | * Fix typos, remove examples from 3.3.5 case (I'm sure that file will get ↵bug26301Simon MacMullen2014-08-062-11/+4
| | | | | | | | | | | | duplicated...)
| | * Try again, with Debian changelog comment filesBlair Hester2014-07-302-0/+27
| | |
| | * Add dir for Debian changelog comments, comment file for 3.3.5, and template fileBlair Hester2014-07-300-0/+0
| | |
| * | merge bug26313 into stable (again)Michael Klishin2014-08-011-4/+1
| |\ \
| * \ \ merge headsMichael Klishin2014-08-011-2/+6
| |\ \ \ | | |_|/ | |/| |
| | * | merge bug26313 into stableMichael Klishin2014-08-011-2/+6
| | |\ \
| * | | | Actually, let's rename that. Yes, a plural, but one that makes more sense.Simon MacMullen2014-07-301-1/+1
| | | | |
| * | | | Merge bug26311Simon MacMullen2014-07-301-0/+68
| |\ \ \ \ | | |/ / / | |/| | |
| | * | | Try again, adding a module this time. Find stuck processes with heuristics.bug26311Simon MacMullen2014-07-301-0/+68
| | | | |
| | * | | Find stuck processes with heuristics.Simon MacMullen2014-07-300-0/+0
| |/ / /
* | | | ...and inline that again.bug26313Simon MacMullen2014-08-111-3/+0
| | | |
* | | | Use a catch-all fn head insteadMichael Klishin2014-08-111-3/+1
| | | |
* | | | Handle exceptions when connection_state = 'starting' the same way we do for ↵Michael Klishin2014-08-111-0/+5
| |_|/ |/| | | | | | | | 'tuning'
* | | Let exception handler do all the handshake failure loggingMichael Klishin2014-08-011-4/+1
| |/ |/|
* | Explicitly log handshake errorsMichael Klishin2014-08-011-1/+4
| |
* | Enforce server-side value when client provided one is 0Michael Klishin2014-08-011-1/+2
|/ | | | | Keeps bogus clients such as node-amqp from ignoring the channel_max limit.
* Merge bug26159Simon MacMullen2014-07-292-3/+26
|\
| * Merge bug25921Simon MacMullen2014-07-282-3/+26
| |\
| | * Explainbug25921Simon MacMullen2014-07-251-0/+3
| | |
| | * Don't allow rabbit_misc:is_process_alive/1 to hang indefinitely if a node is ↵Simon MacMullen2014-07-251-1/+3
| | | | | | | | | | | | incommunicado; we use this in rabbit_amqqueue:on_node_down/1 in a loop!
| | * Merge in stableSimon MacMullen2014-07-251-2/+20
| | |\ | |/ /
| | * Avoid connecting to nodes that are down.Simon MacMullen2014-03-111-2/+20
| | |
* | | Cosmeticsbug26159Michael Klishin2014-07-291-2/+3
| | |
* | | This code will naturally be called just once, eliminate the guardMichael Klishin2014-07-291-7/+2
| | |
* | | Catch errors in vm_memory_monitor:get_total_memory/0 and return 'unknown'Michael Klishin2014-07-251-1/+13
|/ /
* | Merge bug26290Simon MacMullen2014-07-253-7/+56
|\ \
| * | Inlinebug26290Simon MacMullen2014-07-251-8/+4
| | |
| * | Make vm_memory_monitor:parse_line_linux/1 parse lines w/o colonsMichael Klishin2014-07-251-8/+25
| | | | | | | | | | | | Happens with some broken kernel modules.
| * | Tests for vm_memory_monitor:parse_line_linux/1Michael Klishin2014-07-252-0/+36
| | |
* | | Uploaders field change in debian/control to announce Debian Maintainer ↵Blair Hester2014-07-241-1/+1
| | | | | | | | | | | | change from Emile to Blair
* | | Merge bug26293Simon MacMullen2014-07-223-34/+64
|\ \ \ | |/ / |/| |
| * | Actually, hold on to confirms when pausing. It's not inconceivable that we ↵bug26293Simon MacMullen2014-07-221-1/+1
| | | | | | | | | | | | might get a false positive from pause_minority_guard, in which case we don't want to throw data away.
| * | Check for pause minority mode being about to cause a shutdown before sending ↵Simon MacMullen2014-07-223-34/+64
|/ / | | | | | | confirms. In this way we can get rid of the effort to kill all network connections ASAP.
* | Merge bug26292Simon MacMullen2014-07-160-0/+0
|\ \
* | | Further documentation of this approach.bug26292Simon MacMullen2014-07-161-13/+11
| | |
* | | It's probably a good idea to reset "restarts" after we get the message, not ↵Simon MacMullen2014-07-141-3/+4
| | | | | | | | | | | | when we send it; we don't want to jump back into restarting things as normal just because we have scheduled a restart.
* | | Reset restarts before we go round again, otherwise if MaxT is large we will ↵Simon MacMullen2014-07-141-1/+1
|/ / | | | | | | keep looping until it clears.
View Lorry Controller Status