Thanks Tim for the response. Apperantly it looks like this is an issue with AMQ 4.1.2 and 5.8.0. Upon looking for ports being invoked in both of these versions found a JAVA resource that wasn't part of the AMQ code hooking on to any new service that was started.
When did the changes and ran multiple instances on AMQ 5.14.5 it worked like a charm and was able to start and stop them without impacting other services. So will use AMQ 5.14.5 for now. Thank you all for your inputs. -- View this message in context: http://activemq.2283324.n4.nabble.com/How-do-I-Set-Up-Multiple-ActiveMQ-Services-on-one-Windows-Machine-tp4714245p4727023.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
