As a workaround I found setting "initialRecconectDelay=1500" on the failover connection string caused enough delay to avoid the KahaDB from being creating in the default location.
http://activemq.apache.org/failover-transport-reference.html -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
