[ https://jira.terracotta.org/jira//browse/CDV-354?page=comments#action_22304 ] Gary Keim commented on CDV-354: -------------------------------
If, on the server host: % telnet `hostname` 9520 ... shows that it's connecting to a local 127.* address, then you won't be able to monitor the Terracotta Server remotely. The result of the hostname(1) command must be an externally resolvable address if you hope to be able to connect from a remote AdminConsole. > JMX port not available remotely? > -------------------------------- > > Key: CDV-354 > URL: https://jira.terracotta.org/jira//browse/CDV-354 > Project: Community Development > Issue Type: Bug > Reporter: Taylor Gautier > Assigned To: Issue Review Board > > This is the second time on the forums someone has reported problems > connecting the admin console remotely. > ---------------------------- > I'm having a problem connecting remotely to the Terracotta servers with the > Admin Console... It is running on port 9520 > 2007-07-31 08:13:27,379 INFO - JMX Server started. Authentication OFF - > Available at URL[service:jmx:rmi:///jndi/rmi://localhost:9520/jmxrmi] > but I can't connect remotely... is the JMX server configured for > communication from localhost only? > ----------------------------- > Can we check into this to ensure that running our server on windows and on > rhel is able to be connected to by a remote host? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.terracotta.org/jira//secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
