Tomcat/JMX monitoring with SSL

So I gave up on SSL as it turns out the behavior is not what I thought it was and we do not need it. I do have it working great with authentication which is all I need.

Now I just have to figure out why our test server works and our production server doesn't !

my setenv.sh file sources a file set up by ansible...
 

CATALINA_OPTS="-Dcom.sun.management.jmxremote=true \
-Dcom.sun.management.jmxremote.port={{ jira_lm_jmxport }} \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.authenticate=true \
-Dcom.sun.management.jmxremote.password.file={{ jira_lm_jmxpath }}/jmxremote.password \
-Dcom.sun.management.jmxremote.access.file={{ jira_lm_jmxpath }}/jmxremote.access \
-Djava.rmi.server.hostname={{ ansible_default_ipv4.address }}"

I've run tcpdump on the production server and wireshark back on my windows collector and verified that the two are in fact talking to each other on the jira_lm_jmxport

The error indicates that it's timing out. I tried increasing the timeout for jmx on the collector and was still getting a timeout but perhaps I need to try longer...

On Friday I'll be restarting the service after adding these two lines to see if that helps after reading some posts
 

-Dcom.sun.management.jmxremote.rmi.port={{ jira_lm_jmxport }} \
-Dcom.sun.management.jmxremote.local.only=false \