"Modify the "activemq" startup script (in bin) " I did not realize you are expected to modify the start script to allow remote JMX monitoring
now the web console is able to connect via "service:jmx:rmi://localhost/jndi/rmi://localhost:1616/jmxrmi" I don't understand why port 1099 seems to be taken all the time. was there a way to connect jmx using ort 1099? because in the web console documentation, http://activemq.apache.org/web-console.html it keep referring to port 1099. bsnyder wrote: > > On Sun, Feb 7, 2010 at 11:47 AM, bhomass <bhoma...@cox.net> wrote: >> >> Thanks for the reply. >> >> actually, I already got past that step, and realized about not using >> jndi. >> >> the step I am on now is jmx is refused connection. >> >> my situation is similar to many I found on the web. jconsole connects ok >> (by >> pid), jmx client does not. first it indicates lack of rmi server, after >> starting rmi registry manually, it says NameNotFoundException: jmxrmi. >> >> as I try it now, I am not able to start the rmi registry either by >> start rmiregistry or programmatically >> >> LocateRegistry.createRegistry(1099). >> >> I get a Address already in use: >> >> I am getting that ServiceUnavailableException again! > > I believe that this is a matter of proper configuration to expose JMX > remotely. See the following for instructions on how to do use: > > http://activemq.apache.org/jmx.html#JMX-AdvancedJMXConfiguration > > Bruce > -- > perl -e 'print > unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" > );' > > ActiveMQ in Action: http://bit.ly/2je6cQ > Blog: http://bruceblog.org/ > Twitter: http://twitter.com/brucesnyder > > -- View this message in context: http://old.nabble.com/trouble-setting-up-webconsole-on-tomcat-tp27482949p27494275.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
