I run into this issue when deploying an embedded active MQ broker as part of a application based on Apache Camel on a Windows Server 2012R2 host. I followed the advice of posted above and changed the port to which the broker was bound (from 61616 to 6616)