Hi Tony, Instead of using the broker: argument to the bin/activemq script, it may be easier to put the broker config into a separate configuration file and reference that file at startup, e.g.
./activemq xbean:file:../conf/my-broker-config.xml It is easier to further fine tune the broker configuration that way. You can copy and paste the stomp transport connector definition from activemq-stomp.xml or you can simply run the broker using that configuration file ./activemq xbean:file:../conf/activemq-stomp.xml Not sure if the broker: argument to the bin/activemq script still works 100%ly correctly. I just gave it a quick test using ./activemq broker:(tcp://localhost:61613) and the broker would not startup but raise errors. Using a proper xml configuration file may hence be easier. Also, there should not be any problem with enabling JMX if you run the broker standalone. If it runs embedded and the JVM is already JMX enabled, it will register into that JMX context. Hope this helps, Torsten Mielke tors...@fusesource.com tmielke.blogspot.com On Nov 20, 2012, at 1:11 PM, topsweep1506 wrote: > Hi torsten sorry for bein a pain but im gettin stuck with the broker config, > what i was goin to do was make my own config file using the uri statement > (broker:(tcp://localhost:61616,network:static:tcp://remotehost:61616)?persistent=false&useJmx=false) > without using the jmx as i think thats were im getting the problems with > java > > Only problem is im not sure how to do it, if i run the conf\activemq.xml > broker file it takes me to a explorer window and thats it > > And how would i configure the uri statement to get a stomp listener on port > 61618 > > Sorry for all the questions > > Thanks Tony
