After configuring your atom to use JMX and you are leveraging password authentication the atom does not start.
When setting up your atom to authenticate a JMX connection using a password the atom will not start if the password file is not set up correctly. If the password file is not set up correctly the underlying JAVA libraries will shut the application down and you will not see a error message the indicates the problem is the configuration of the password file.
Because there are cleartext passwords stored in the jmxremote.password file, this file must be read and writable only by the owner; otherwise, JAVA forces the program to close immediately.
The general guidelines to setting up your JMX connection to leverage a password can be found at Enabling remote JMX on an Atom.
In order to avoid your atom from shutting down you need to ensure the jmxremote.password is owned by the same user that your atom is running as. For example if you are running your atom on a windows platform as a service under the Local Admin account the permissions on the jmxremote.password file should be set to 'Full control' to the local admin account and the owner also needs to the local admin account. See below for a sample of the permissions on the jmxremote.password.
The more secure technique for securing your JMX connections would be to use SSL; however, if you simply want a more secure mechanism than no authentication in a development or test environment then leveraging password protection is an appropriate option.