. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 33.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 33.1. Benefits 33.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 33.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 33.1. Benefits 33.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 33.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 33.1. Benefits 33.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 33.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 33.1. Benefits 33.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 33.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 33.1. Benefits 33.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 32.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 32.1. Benefits 32.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 32.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 32.1. Benefits 32.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 32.1. Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Huge update involving a significant refactoring of the addressing model yielding the following benefits: ◦ Simpler and more flexible XML configuration. ◦ Support for additional messaging use-cases. and local-only components - you don’t need to federate everything if you don’t want to. 32.1. Benefits 32.1.1. WAN The source and target servers do not have to be in the same cluster which makes federation

Huge update involving a significant refactoring of the addressing model yielding the following benefits: Simpler and more flexible XML configuration. Support for additional messaging use-cases. Eliminates ensure durable writes was different (and slower) from the fsync used is case of NIO journal. It benefits by the configuration of OS huge pages, in particular when is used a big number of journal files messages would be required to go to a queue on a single node. This would effectively nullify the benefits of clustering. Also, the arrival of messages on and and redistribution of those messages from nodes

Huge update involving a significant refactoring of the addressing model yielding the following benefits: Simpler and more flexible XML configuration. Support for additional messaging use-cases. Eliminates ensure durable writes was different (and slower) from the fsync used is case of NIO journal. It benefits by the configuration of OS huge pages, in particular when is used a big number of journal files messages would be required to go to a queue on a single node. This would effectively nullify the benefits of clustering. Also, the arrival of messages on and and redistribution of those messages from nodes