ARTEMIS-1360 Update config-reload documentation on queues

Updated details on max-conumsers and purge-on-no-consumers now these fields  on queue update on reload.
This commit is contained in:
Michael Andre Pearce 2017-08-30 07:16:06 +01:00 committed by Clebert Suconic
parent 5fead3e4bc
commit 91abc8770c
1 changed files with 2 additions and 2 deletions

View File

@ -204,8 +204,8 @@ Operation | Add | Delete | Update
`<queues>` | X(no more than one is present) | Deleting it means delete (undeploy) all queues from running broker. | N/A
`<queue>` | A new queue is deployed after reloading | The queue will be undeployed after reloading. | N/A
attribute `name` | N/A | X | A queue with new name will be deployed and the queue with old name will be updeployed after reloading (see Note above).
attribute `max-consumers` | N/A | No effect unless starting broker | No effect unless starting broker
attribute `purge-on-no-consumers` | N/A | No effect unless starting broker | No effect unless starting broker
attribute `max-consumers` | If max-consumers > current consumers max-consumers will update on reload | max-consumers will be set back to the default `-1` | If max-consumers > current consumers max-consumers will update on reload
attribute `purge-on-no-consumers` | On reload purge-on-no-consumers will be updated | Will be set back to the default `false` | On reload purge-on-no-consumers will be updated
attribute `address` | N/A | No effect unless starting broker | No effect unless starting broker
attribute `filter` | N/A | No effect unless starting broker | No effect unless starting broker
attribute `durable` | N/A | No effect unless starting broker | No effect unless starting broker