Opscenter agent fails to connect to the local cassandra node via JMX
When JMX authentication is enabled on a Cassandra cluster, the agent fails to connect when a complex password contains some special characters. The following entries are reported in the agent.log
INFO [StompConnection receiver] 2015-06-17 11:20:03,542 New JMX connection (myserver1.7199) WARN [StompConnection receiver] 2015-06-17 11:20:03,558 Error when trying to match our local token: java.lang.SecurityException: Authentication failed! Invalid username or password
This is a known issue, and covered in the following internal jira:
OPSC-5738 - Using special characters in JMX passwords causes agent connectivity issues
Change the JMX password to exclude the special characters.
At the time of writing this article OPSC-5738 was not resolved.