THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
No Format |
---|
queuex.<name> = {key='value', ...} destinationx.<name> = <address>[ # destination without options destinationx.<name> = <address>; {a='b', c={x='y', z='w', ...}, ...} # destination with options |
- In a production environment the queues will most likely be pre-configured using an admin tool. However if you need to create queues dynamically the queuex definition allows you to configure your queues in the jndi.properties file it self. It's just a simple key-value pair.
...
The options here are not a static list. The format is extensible and new options could be introduced any time in the future.
- queuex
- name : name of the queue
- durable
- exclusive
- auto-delete
- alt-exchange
- no-local (??)
- qpid.max_count
- qpid.max_size
- qpid.policy_type { reject | flow_to_disk | ring | ring_strict }
- qpid.last_value_queue {1}
- qpid.last_value_queue_no_browse {1}
- qpid.LVQ_key
- qpid.persist_last_node {1}
- qpid.queue_event_generation { 0,1,2 } (0 to disable,1 to replicate, only enqueue events)
- destinationx.
- filter
- filter-type
- msg-credits
- byte-credits
- sync-ack
- sync-publish {persistent|all}
- bindings - format as follows - a Qpid specific extension for binding a queue to multiple exchange/binding key pairs
No Format { bind={exchange-name=<name>, binding-key=<key>, [args={a='b',c='d',...}]} [, bind={}] }