Re: Automated queue creation within a swiftlet

OK; regarding startup - I thought that might be the case.

Queue names changing isn't really the issue. This is a public forum, so I can only say so much, but suffice to say that our business logic demands that we create and remove quite large numbers of queues dynamically based on changes made to centralised configuration for our Extension Swiftlet; configuration that must sit outside of SwiftMQ as it affects several elements of our architecture. Additionally, business rules demand that we cannot restart SwiftMQ (and our extension swiftlet in particular) when changes are made to this centralised configuration - it must be propagated and hot-deployed across multiple SwiftMQ/Swiftlet instances and be able to support creation of any necessary resources such as new queues. A set of commands in config.xml is completely unsuitable for this purpose - this project is about automation and removing the need for our operations team to manually change SwiftMQ XML configuration as part of their day-to-day activities; since it's time consuming, risky, and non-scalable.

I don't want to go down the system queues route because it's poorly documented; I don't really understand it; and the current production system uses regular queues (albeit statically managed). Additionally, if there is a startup problem with the Extension Swiftlet I can also not afford for queues to not be created/visible/available to other external QueueProducers which rely on these queues, which seems to be the case with system queues.