Re: Automated queue creation within a swiftlet

Sorry, I'm not really sure what you're saying or implying. While I understand that the SwiftletManager blocks during startup, the thread dump doesn't indicate anything else is waiting for that lock - so it doesn't seem to explain why the CLI (sometimes) times out. The code and thread dump indicates the CLI interface is waiting for a response that it never receives; and the sporadic nature of the problem indicates there is a timing issue; i.e. sometimes it's making a request before some aspect of the router is ready to receive it.

The problem definitely goes away if I use AsyncTasks; but this is suboptimal as I want to fail startup/deployment if queues cannot be created for any reason and handling this asynchronously does not really give me the behaviour I want. If I must do say due to an indeterminate router startup/deployment performance, then I will do so - but I wanted to understand why this was happening.

We haven't configured our swiftlet in any "special" way; its' just defined as another swiftlet in the router config, per the documentation at docs/router/swiftletapi/deploy/index.html. It doesn't indicate any choice other than hot deployment as a possibility.