Followup. So we got around this issue by suplying the Hashtable parameter in the construction of our InitialContex and then specifying all of the hosts and thier HAJNDI ports under the PROVIDER_URL key.
This seems like a hack since now I need to maintain these in a properties file (since we deploy this application to different sites).
Are your clients running inside the application server itself? If so, just providing localhost:1100 as the provider URL should work. Or are you using the -b switch to bind ports to a particular IP, in which case that won't work.
we see the queues attempt to deploy but instead drop into their waiting state.
That doesn't sound right; queues shouldn't even attempt to deploy unless they are on the master node. Are you deploying your queues from the deploy-hasingleton directory?