Does that apply for a hostname of localhost like the OP was using? And can you give more details about exactly what switched, and in what version of the JVM? I'd have expected hostname resolution to be handled by the OS and/or a service like DNS, and that therefore the behavior would be the same for all versions of the JVM, so I'd like to better understand what changed so I'll know what behavior to expect from different versions.
Tim On Sep 23, 2016 1:04 PM, "Matt Pavlovich" <mattr...@gmail.com> wrote: > The sounds like a hostname to IP resolution. Newer JDK's require a lookup > for the hostname to an IP for JMX. Many cloud and VM instances do not set > this by default. > > For example, if you have your hostname vm-123456 > > 1. Add entry to /etc/hosts > 127.0.0.1 vm-123456 > > 2. Restart the JVM > > On 9/22/16 7:53 PM, mathewvino wrote: > >> activemq : apache-activemq-5.14.0 >> jconsole using jdk1.7 >> >> I have started the activemq which comes with the jetty server. Minor >> change >> to make the jmx enable is just change <managementContext >> createConnector="true"/> default is false(activemq.xml) --- I am using the >> latest version 5.14.0 >> >> when i start i am seeing the message >> JMX consoles can connect to >> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi >> >> So I start Jconsole use remote process and use >> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi >> >> with no password : it says secure/insecure connection failed: not sure >> where the problem is >> >> Any help is really appreciated >> >> <http://activemq.2283324.n4.nabble.com/file/n4716819/activemq.png> >> >> >> >> >> >> >> >> -- >> View this message in context: http://activemq.2283324.n4.nab >> ble.com/jconsole-using-activemq-tp4716819.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > >
