removing the jmx parameters by default

aws_bitbucket_mesh_node.yml

@@ -14,11 +14,9 @@
       - 'Environment=MESH_HOME={{ atl_home_base }}/{{ atl_product_edition }}'
       - 'Environment=JAVA_HOME=/usr/lib/jvm/java'
       - 'Environment=JRE_HOME=/usr/lib/jvm/java'
-      - 'Environment=JMX_REMOTE_AUTH=password'
-      - 'Environment=JMX_PASSWORD_FILE={{ atl_home_base }}/{{ atl_product_edition }}/jmx.access'
       - 'Environment="JVM_SUPPORT_RECOMMENDED_ARGS=-Dmesh.enabled=true -Dplugin.bitbucket-git.mesh.sidecar.child-process=false -Dcom.sun.management.jmxremote.port=4444 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath={{ atl_home_base }}/{{ atl_product_edition }}/log"'
       - 'Environment=JVM_MAXIMUM_MEMORY={{ atl_jvm_heap }}'
-      - 'PassEnvironment=JMX_REMOTE_AUTH JMX_PASSWORD_FILE JAVA_HOME'
+      - 'PassEnvironment=JAVA_HOME'
 
     atl_startup_exec_path: "{{ mesh_install_dir }}/current/bin/start-mesh.sh"
     atl_stop_exec_path: "{{ mesh_install_dir }}/current/bin/stop-mesh.sh"

roles/bitbucket_mesh/tasks/main.yml

@@ -38,7 +38,6 @@
   register: mesh_extract
   when:
     - maven_download.changed | bool
-    - not maven_download.failed
 
 # the owner/group on the unarchive above isn't thorough
 - name: adjust permissions on the extracted directory
@@ -56,11 +55,3 @@
     state: link
   when:
     - mesh_extract.changed | bool
-
-- name: touch the jmx password file
-  ansible.builtin.file:
-    path: "{{ atl_home_base }}/{{ atl_product_edition }}/jmx.access"
-    state: touch
-    owner: "{{ atl_product_user_uid }}"
-    group: "{{ atl_product_user_uid }}"
-    mode: 0600