Looks like the SUNJMX env variable is set to -Dcom.sun.management.jmxremote.port=1099 make sure it's not for the activemq-admin script.
On Wed, May 14, 2008 at 8:24 AM, andrewh <[EMAIL PROTECTED]> wrote: > > Hi, thanks for the reply. > > > j0llyr0g3r wrote: >> >> kill the activemq-process and look via >> >> netstat -tulpen | grep 1099 >> >> which services already occupies this port. >> > > The only service using that port, according to netstat, is the java process > that activemq is running within. > > $ sudo netstat -tulpen | grep 1099 > Password: > tcp6 0 0 :::1099 :::* LISTEN > 0 20451792 2207/java > > $ ps -ef | grep 2207 > root 2207 1 21 12:40 pts/0 00:08:25 > /usr/local/jdk1.6.0_06/bin/java -Xmx2048M > -Dorg.apache.activemq.UseDedicatedTaskRunner=true > -Dderby.system.home=/usr/local/fuse-message-broker-5.0.0.11/data > -Dderby.storage.fileSyncTransactionLog=true > -Dcom.sun.management.jmxremote.port=1099 > -Dcom.sun.management.jmxremote.ssl=false > -Dcom.sun.management.jmxremote.authenticate=false > -Dactivemq.classpath=/usr/local/fuse-message-broker-5.0.0.11/conf; > -Dactivemq.home=/usr/local/fuse-message-broker-5.0.0.11 > -Dactivemq.base=/usr/local/fuse-message-broker-5.0.0.11 -jar > /usr/local/fuse-message-broker-5.0.0.11/bin/run.jar start > > Any ideas? > -- > View this message in context: > http://www.nabble.com/activemq-admin-stop---port-already-in-use-tp17210936s2354p17229811.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
