Sorry Matt, I haven't seen your answer :) I have posted an update :)
Regards -- Jean-Baptiste Onofré [EMAIL PROTECTED] BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net On Thu 23/10/08 19:36 , mattrpav wrote:: Sanjay- Its technically possible, but requires some attentiveness. There are two approaches: 1. An IP per instance. Each instance listens on the same port numbers, but on specific IPs, not *:8080, but 10.0.0.10:8080 and 10.0.0.11:8080. 2. Change the ports of the second instance to not conflict with the first. Technically, you should be able to have two instances tied to their own IP, but I've never proven that all the components support that properly. Below is the approach for changing all the ports in the second instance. Leave the first one alone. Find files that have a port config: find $SM_HOME/conf -type f -exec grep port {} \; For sure these files.. conf/activemq.xml conf/servicemix.properties conf/servicemix.xml NOTE:: *** BE SURE TO SETUP THE ACTIVEMQ PORTS CORRECTLY *** All heck breaks loose, if you have one SM instance sending messages to another's ActiveMQ. and if you have DEBUG enabled, you'll need to change the JVM debug port in bin/servicemix DEFAULT_JAVA_DEBUG_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 Change the '5005' to something else in the second instance. Test just the SM setup without any deployed SA's. Once that works, you have to remember to update you SA's to listen on different ports.. 8081 vs 8080, etc. Matt Pavlovich -- View this message in context: http://www.nabble.com/Installing-Multiple-instances-of-servicemix-tp20134120p20135968.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
